Shell Programming and Scripting

It would seem that:

Code:

tail -1 log | grep up

could be discarding diagnostics indicating why rndc failed. Is there some reason why something like:

Code:

rndc -k ${RNDC_KEY} -s ${DNS_SERVER} status > $some_temp_file 2>&1 || cat $some_temp_file

wouldn't give you a better indication of what might have gone wrong? Or, if you don't want to see normal output, but want to see diagnostic output, have you considered something simpler, like:

Code:

rndc -k ${RNDC_KEY} -s ${DNS_SERVER} status > /dev/null

(which is not redirecting standard error at all).

Problem is that its a parent script that launches this one so we don't get to see standard output or standard error on the term. That way the temp file would really help. Each time i try to run it myself it is always succefull.

I even tried this to see if it was not a rndc overload problem

Code:

for (( x=1; x<=500; x++ )); do rndc -k <key> -s <serverip> status| grep up; echo $?; done

And not a single fault.

Maybe i could put my check in a loop saying well if it fails the first time maybe try again in like 2-3 seconds? I'm the first one to scream at people using sleep in their script but maybe it's time i revise my position

Eh, it's like log files. If you don't know what you're looking for, you don't know what's safe to throw away. At least this is temporary...

I get it.... i've modified the rndc to keep the important stuff. Of course it makes sense.

Will let you guys know what i can find out. Thanks again.