3 ms·
There are a lot of you statements in this rant. It reads like a junior sysadmin who just learned (or failed to learn) an important lesson about using >/dev/nul
by woleium 3y ago
There are a lot of you statements in this rant.
It reads like a junior sysadmin who just learned (or failed to learn) an important lesson about using >/dev/null 2>&1 at the end of commands in their scripts (or, even better, how to push output to a log file with the logger command or similar)
- kps 3y agoIt's unfortunately not rare to find programs that write diagnostics to standard output instead of standard error.
- deredede 3y agoThat's fair, but the solution to that problem is to print warning messages on standard error, not to make them fatal errors.
- ynik 3y agoIt's also not rare to find wrapper scripts that check "was there any output to stderr?", and if so, consider the program to have failed. Warnings are not errors, but also not output, so there isn't a good way to report them in the stdout/stderr model (but stderr is still better than stdout).
- JdeBP 3y agoEven in 2007, Chris Siebennmann wasn't a junior system administrator. (-: