>> So I think when using inetd in check mode, it is an utility and the >> config will go to stdout, and the errors about the parsing to stderr >> [...]
> IMHO, if check + -f foreground; errors to stdout/stderr, > and if check + (background default); output to syslog. I see no particular use for dump-to-syslog, so I would do that only with a specific particular option to do so. Perhaps I'm misinterpreting what check mode would print. > If check mode is used in an rc.d script (for example), dumping a lot > of errors to stderr can ruin "clean" rc.d output, If your inetd config has syntax errors, you've got bigger problems than the asesthetics of your rc output. I see no use for check mode on routine boot-time startup; if check mode would fail, so would normal startup, so the check run brings no additional value. > and if the stderr errors occur at startup, you may not have easy > access to errors printed to stderr on boot, whereas you generally > have the syslog. I would leave that sort of diagnosis to a manually-run check after startup. A report of the presence of a fatal syntax error to syslog, that's reasonable. Perhaps even with the error. But full check diagnostic output seems inappropriate for syslog, to me. /~\ The ASCII Mouse \ / Ribbon Campaign X Against HTML mo...@rodents-montreal.org / \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
