bash: feeding input to a script from a text file

grail · 11-18-2010, 06:20 PM

oops

Sorry, completely forgot about the yes / no questions.

Try this instead:

Code:

exec 3<$project

while read -r JOBID <&3
do
    <your stuff here>
done

exec 3<&-

Also, you may wish to make the yes / no questions more robust as a user may enter y, Y, yes, Yes or even ok.
Perhaps you should suggest possible answers (help get rid of things like ok) and then look at controlling the case (upper or lower)

tuxdev · 11-18-2010, 06:32 PM

Here's a somewhat simpler way to do the same thing:

Code:

while read -u 3 -r JOBID
do
    <your stuff here>
done 3<"$project"

grail · 11-18-2010, 08:11 PM

Thanks tuxdev ... hadn't seen that one before

GrapefruiTgirl · 11-19-2010, 05:12 AM

Thanks to you both in posts #16 and #17 - nifty exec tricks to keep in back of mind..

faizlo · 11-19-2010, 12:15 PM

As far as I can tell, I am still using this script:

Code:

#! /bin/bash
for JOBID in `cat jobs-ids.txt`
do
./make_recovery.sh $JOBID

done

which is kind of auto-manual. It feeds the jobs-ids one by one, but I have to answer with y (if I really want to say y) for any of the questions in the main script, otherwise a hit on enter and I move to the next job id.

As you may know now, I have few questions that should be answered with y or the script will abort.
For the first question:

Code:

echo "Make a recovery def for project: ${project}"
echo "First, look at the project summary."
check

The answer should be y

then the script goes to the second question. This time again, the answer should be y and the output message may or may not contain the statement "NO FILES TO RECOVER".

What I hope to do is to have the first two answers as y automatically, and when the message "NO FILES TO RECOVER" is spelled out, the script should proceed to the next JOBID in the jobs-ids.txt. How is this possible.

~faizlo

grail · 11-20-2010, 01:22 AM

So change the script to auto those parts and check for your string "NO FILES TO RECOVER".

This would however mean moving away from your for loop in last post.

faizlo · 12-02-2010, 05:40 AM

Hi again,

so I had to it manually as I described in my last post. But, since this would really help me a lot for all my jobs, I wonder if it is possible to get some help from you to make it fully functional and fully processed without me having to reply with either y or [enter]

How may I start this?

catkin · 12-02-2010, 05:59 AM

Try:

Code:

#! /bin/bash
for JOBID in `cat jobs-ids.txt`
do
    yes | ./make_recovery.sh $JOBID
done

grail · 12-02-2010, 06:06 AM

I would edit the jobs-id.txt file so it looks like:

Code:

ID1 Y Y
ID2 Y Y

This way you can change the while loop:

Code:

while read -r JOBID PROJECT DIMS
do
     <your stuff here and use PROJECT and DIMS to answer first 2 questions if they are there>
done<jobs-id.txt

faizlo · 12-02-2010, 07:10 AM

So, is there a way to check the output for the certain string "STRING" and decides the answer based on it?

grail · 12-02-2010, 07:54 AM

Yes you should be able to capture the output in a variable and test its equality against your chosen input:

Code:

if [[ "$VAR_WITH_OUTPUT" == "$VAR_WITH_INPUT_TO_TEST" ]]
then
    <do stuff here if true>
fi

catkin · 12-02-2010, 08:07 AM

Quote:

Originally Posted by faizlo

So, is there a way to check the output for the certain string "STRING" and decides the answer based on it?

Yes. Assuming my previous suggestion worked:

Code:

#! /bin/bash
for JOBID in `cat jobs-ids.txt`
do
    case $( yes | ./make_recovery.sh $JOBID) in
        *'first string you are looking for'* )
            <whatever you want when it is found>
            ;;
        *'second string you are looking for'* )
            <whatever you want when it is found>
            ;;
        * )
            <whatever you want when none of the strings are found>
            ;;
    esac
done

The * in front and after the strings makes the case statement match them if they appear anywhere in the output.

faizlo · 12-02-2010, 08:10 AM

@grail:

the output is 10s of lines, if not 100s, but the final 4 lines contain the string "NO FILES TO RECOVER", so I guess I need grep for that.
I am sorry, but I am getting confused now.
I have tried to google this but did not know which term to use for search, I used "check output for a certain string" but couldn't find what I am looking for.

~faizlo

faizlo · 12-02-2010, 08:11 AM

@catkin:

I will check that.

~f

grail · 12-02-2010, 08:13 AM

So which command is returning the 10s / 100s of lines? If you know it will definitely be in the last line then a simple tail command will show you what you want.