tisdagen den 23 september 2003 20.10 skrev Oden Eriksson:Hi.
Anyone else seing this:
# /etc/rc.d/init.d/named restart Stopping named: [FAILED] Starting named: [ OK ]
i never used bind-chroot myself anyway reading /etc/rc.d/init.d/function i found this piece of code in killproc function.
# Avoid killing processes not running in the same root [ -n "$pid" ] && pid="`inmyroot $pid`"
this might be the culprit.
why don't we use rndc stop in the initscript for named?
besides bind-chroot scripts removes rndc conf from /etc, so root cannot use rndc anymore. great idea!!! why the hell does bind-chroot have to muck with my syslogd.conf, since my chrooted bind syslogs without any problem?
L.
--
Luca Berra -- [EMAIL PROTECTED]
Communication Media & Services S.r.l.
/"\
\ / ASCII RIBBON CAMPAIGN
X AGAINST HTML MAIL
/ \