Date: Thu, 10 Mar 2005 23:36:23 -0500 (EST) From: "Jerry Bell" <jbell@stelesys.com> To: "comm" <comm@rwx.ca> Cc: freebsd-questions@freebsd.org Subject: Re: chroot jail and syslogd Message-ID: <2678.24.98.86.57.1110515783.squirrel@24.98.86.57> In-Reply-To: <20050310214125.2FDD6E79D@cmlapp400.van.ca.siteprotect.com> References: <20050310214125.2FDD6E79D@cmlapp400.van.ca.siteprotect.com>
next in thread | previous in thread | raw e-mail | index | archive | help
I have a very similar setup with bind run inside a chroot jail. I experience a similar problem if I set up named to use /var/run/log. I commected it out and put "syslog daemon" in its place and it works like a champ. Sadly, I've not found the time to spend figuring out why it doesn't work otherwise. Jerry http://www.syslog.org > channel audit_log { > > // Send the security related messages to a separate file. > > file "/var/run/log"; > > severity debug; > > print-time yes; > > };
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2678.24.98.86.57.1110515783.squirrel>