I want to run named chrooted, but I cannot start through /etc/rc.d/init.d/named. This is a slave named, and at most only one named-xfer succeeds. The commandline within /etc/rc.d/init.d/named is daemon /home/chroot/named/usr/sbin/named -u named -g named -t /home/chroot/named -c /named.conf In syslog, for each failed named-xfer, I see a signal 13 (SIGPIPE). If I start named from the commandline (without nice and initlog), then it runs fine and all of the named-xfers succeed. I tracked down the problem to initlog. If I start the command initlog -c "/home/chroot/.../named -u named ..." Then I have the same problem. However, if instead of -c I use -r, then named will start properly. As a side note, the -q switch is not documented in the man page. ;-) Solution? For named, just start with the -r switch. Unfortunately I couldn't really understand the difference between -c and -r and I don't know what else it would do. Thank you for your time, Vilmos Soti
-c runs the command and logs its output. -r runs the command, and initlog stays around looking for things to log on its own stdin. Presumably what's happening is that bind is closing its stdin, so initlog exits.
*** Bug 25269 has been marked as a duplicate of this bug. ***
(make that, bind is closing its stdout and stderr.)
Closing out bugs on older, no longer supported, releases. initlog is no longer in the current devel tree, so it is unlikely to change.