Ah well, one never stops learning. I don't think I've ever had the occasion to run something with stdout/stderr closed. Redirected to /dev/null, yes... closed, no.
You would need to be pretty confident that "command" was going to acheive completion of what you ask it to do, even should it barf on the i/o error it will be getting if it attempts to output anything.
I.e. where
Code:
command >/dev/null 2>&1
would always perform "command" to completion, discarding all output,
Code:
command >&- 2>&-
might fall over halfway through, because of a failed attempt to output to stdout.
_________________
"Striking up conversations with strangers is an autistic person's version of extreme sports."
Kamran Nazeer
23 Nov 2007, 4:53 pm
