Date: Thu, 16 May 1996 09:08:33 -0700 From: patl@asimov.volant.org To: freebsd-questions@freebsd.org Subject: Syslog -vs- chroot Message-ID: <9605161608.AA23936@asimov.volant.org>
next in thread | raw e-mail | index | archive | help
For various reasons I'm trying to run some daemons in a chrooted environment. I seem to have everything set up properly to allow them to run; but the log info they send via syslog are lost. I assume this is because syslog is trying to connect via the unix domain socket, which doesn't exist in the chrooted environment. Is there any way to force it to use the inet domain socket instead? Failing that, do any of you know of any other way for me to handle this? I have considered spawning another syslog daemon in the chrooted environment, and directing it to forward everything to loghost; but I'd rather avoid that if possible - I expect to have several distinct chroot environments and really don't want a syslog process for each one... Thanks, -Pat My opinions are my own. For a small royalty, they can be yours as well... Pat Lashley, Senior Software Engineer, Henry Davis Consulting patl@Phoenix.Volant.ORG || http://Phoenix.Volant.ORG/ || lashley@netcom.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9605161608.AA23936>