Shell Programming and Scripting

This is why you're supposed to use the return code instead of making the computer swallow the human-readable error messages. There's lots of ways the printing could work, but only one way a return code works.

In this case, it must be printing these messages to standard error. That's the place things the computer isn't supposed to be handling like this go. We can force the script to intercept these things it's not supposed to handle with a redirection.

Code:

while read NODE PORT UID PWD
do
        cfsend n:"${NODE}" port:${PORT} uid:${UID}  pwd:${PWD} pn:CHCKDIR ud:5563 trtype:c rcmd:"pwd" 2>&1 | grep -iq "failed communicating with partner" && echo "PS is down on $NODE"
done < table > output.log 2>/dev/null

Hi Corona,

I passed the cfsend command line output into one log file,from there i did grep command and written a logging to find only
"Failed Communicating with partner" and corresponding node name

its working fine for couple of node names,will try add more nodes in the txt file

And i have one question wanna confirm with you :when passing values from the txt file-how do i separate the values(node,port,uid and pwd)

i am thinking using a space between the values.
Exmp....

node port uid pwd
node port uid pwd
node port uid pwd

is that correct or any other way?

Code:

# for space-separated file
while read NODE PORT UID PWD
do
...
done < datafile

# for comma separated file
while IFS="," read NODE PORT UID PWD
do
...
done < datafile

#etc

thanks