On Fri, 23 Feb 2001, Benjamin Scott wrote:
> After doing this, named will no longer write messages to the syslog daemon,
> presumably because it is chroot'ed and cannot access /dev/log. I have not
> solved this issue yet, but if you are using custom named channels and log
> files instead of the default syslog, you will not be affected.
Since someone already pointed out, the OpenBSD folk figured this part
out. According to the "Chroot-BIND HOWTO" OpenBSD intoduced the '-a' flag
which "Specif[ies] a location where syslogd should place an additional log
socket." RH6.2 appears to have this feature as well. Tacking the
following onto the syslog startup line should work:
"-a [named-chroot-path]/dev/log"
More precise instructions can be found at:
http://www.nexttime.com/LDP/HOWTO/Chroot-BIND-HOWTO-2.html#ss2.5
> I hope this helps someone!
Thanks again, Ben, for actually making this task look as easy as it
should be. The HOWTO is a great document, but just verbose enough to be
daunting.
--
-Matt
Go the extra mile -- It makes your boss look like an incompetent slacker.
**********************************************************
To unsubscribe from this list, send mail to
[EMAIL PROTECTED] with the following text in the
*body* (*not* the subject line) of the letter:
unsubscribe gnhlug
**********************************************************
