Date: Tue, 28 Sep 2004 06:38:24 -0700 (PDT) From: Doug Barton <DougB@FreeBSD.org> To: Makoto Matsushita <matusita@jp.FreeBSD.org> Cc: current@FreeBSD.org Subject: Re: HEADS UP: named now runs chroot'ed by default Message-ID: <20040928063428.O5729@ync.qbhto.arg> In-Reply-To: <20040928214106F.matusita@jp.FreeBSD.org> References: <20040928025635.Q5094@ync.qbhto.arg> <20040928214106F.matusita@jp.FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 28 Sep 2004, Makoto Matsushita wrote:
>
> DougB> Comments and suggestions are welcome, but please try to keep the
> DougB> bikeshedding about specific bits down to an absolute minimum.
>
> One question: what do you think about named(8)'s syslog messages?
I think they are very important. :)
> It seems that current configuration doesn't consider that -- chrooted
> named(8)'s syslog messages go to nowhere.
I need to amend the instructions to say:
/etc/rc.d/named stop
/etc/rd.d/syslogd stop
...
/etc/rc.d/syslogd start
/etc/rc.d/named start
The syslogd script already has the logic to create the socket if named
shows up chrooted in rc.conf.
Thanks for the reminder,
Doug
--
This .signature sanitized for your protection
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040928063428.O5729>