Comments on: On handling logging in a script http://www.dannorris.com/2008/01/11/on-handling-logging-in-a-script/ Thu, 20 Nov 2008 07:27:23 +0000 http://wordpress.org/?v=2.6.3 By: billy http://www.dannorris.com/2008/01/11/on-handling-logging-in-a-script/#comment-862 billy Fri, 18 Jan 2008 00:55:38 +0000 http://www.dannorris.com/2008/01/11/on-handling-logging-in-a-script/#comment-862 no kilt no way. too cold, the boyz will freeze. no kilt no way. too cold, the boyz will freeze.

]]> By: Dan http://www.dannorris.com/2008/01/11/on-handling-logging-in-a-script/#comment-850 Dan Fri, 11 Jan 2008 13:54:55 +0000 http://www.dannorris.com/2008/01/11/on-handling-logging-in-a-script/#comment-850 That's a nice way to handle it. I don't agree that it makes the script code easier to read with lots of parens hanging around, but I still think it's a useful technique--I like the filtering too. Thanks for the nice tip! That’s a nice way to handle it. I don’t agree that it makes the script code easier to read with lots of parens hanging around, but I still think it’s a useful technique–I like the filtering too.

Thanks for the nice tip!

]]> By: Nigel Thomas http://www.dannorris.com/2008/01/11/on-handling-logging-in-a-script/#comment-849 Nigel Thomas Fri, 11 Jan 2008 09:55:48 +0000 http://www.dannorris.com/2008/01/11/on-handling-logging-in-a-script/#comment-849 Dan Another approach (which also works on Windows) is to place the commands you want to log into a bracketed section ( commands to be logged more commands to be logged ) > $LOG This has the added benefit on *nix that you can easily tee and grep the output. So you can log *everything* to a file, but filter out (say) significant progress and error messages. I tend to start my messages with == (the more equals signs, the more important) and then you can filter messages by how many == they have: ( commands ) | tee $log | grep "^===" Of course on *nix you can also redirect stderr at the same time in the usual way(s) eg: ( commands ) >2&1 >$LOG I think using brackets (braces) like this is easier to read - and you can nest the brackets too. Just make sure you match brackets properly. Regards Nigel Dan

Another approach (which also works on Windows) is to place the commands you want to log into a bracketed section

(
commands to be logged
more commands to be logged
) > $LOG

This has the added benefit on *nix that you can easily tee and grep the output. So you can log *everything* to a file, but filter out (say) significant progress and error messages. I tend to start my messages with == (the more equals signs, the more important) and then you can filter messages by how many == they have:

(
commands
) | tee $log | grep “^===”

Of course on *nix you can also redirect stderr at the same time in the usual way(s) eg:

(
commands
) >2&1 >$LOG

I think using brackets (braces) like this is easier to read - and you can nest the brackets too. Just make sure you match brackets properly.

Regards Nigel

]]>