Erich Schubert schrieb: > Note that some init systems (such as minit) expect daemons to use > stdout/stderr for logging.
This is probably the hardest thing to cater for. Though I don't exactly understand what the advantage of this "log through fd1/fd2" is. It doesn't allow filtering by severity as much as syslog does. Also it means that I can't have the daemon log into different files depending on the part of the daemons activities (think different virtual hosts in http/ftp servers). So what exactly do I gain by this? The only thing I can see is that the initd in use can see the error messages of $daemon. But I'm not exactly sure what this would help with. > So getting a good handling of I/O (btw, one thing where sysvinit > really sucks...) right is one of the more difficult things here. True, I think. However, if we want to support sysvinit plus alternatives, we probably need to support different IO/logging styles, too. At least if someone can explain the advantage of logging through STDOUT/STDERR and initd. regards, Sven _______________________________________________ initscripts-ng-devel mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/initscripts-ng-devel
