Date: Tue, 6 May 1997 21:50:37 -0400 From: John Capo <jc@irbs.com> To: Dev Chanchani <dev@wopr.inetu.net> Cc: freebsd-isp@FreeBSD.ORG Subject: Re: Syslogd/Chroot() Questions. Message-ID: <19970506215037.34284@irbs.com> In-Reply-To: <Pine.BSF.3.95q.970505213619.10297A-100000@wopr.inetu.net>; from Dev Chanchani on Mon, May 05, 1997 at 09:38:55PM -0400 References: <Pine.BSF.3.95q.970505213619.10297A-100000@wopr.inetu.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Quoting Dev Chanchani (dev@wopr.inetu.net): > I have questions about syslog in regards to programs that are chroot'ed. > Can I just create another chroot()'ed syslog.conf and point everything > back to the main server via udp? Should I run another syslogd and tell it to create > its local socket in /chroot/dev/log and not bind to a udp port again? > I had occasion to use a chrooted syslogd recently. I modifed syslogd.c to not bind a udp socket or open /dev/klog. I let it create /dev/log in the chrooted space. Worked fine. John Capo IRBS Engineering
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19970506215037.34284>