Date: Fri, 17 May 1996 20:53:47 GMT From: James Raynard <fqueries@jraynard.demon.co.uk> To: patl@phoenix.volant.org Cc: freebsd-questions@freebsd.org Subject: Re: Syslog -vs- chroot Message-ID: <199605172053.UAA27032@jraynard.demon.co.uk> In-Reply-To: <9605161608.AA23936@asimov.volant.org> (patl@asimov.volant.org)
next in thread | previous 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. I believe so. The standard technique is to call openlog() before chroot(), but presumably everything gets chroot()'d before the daemon even starts up. > Is there any way to force it to use the inet domain socket instead? Hmm. There's a 'syslog 514/udp' entry in /etc/services - I don't know if that's any use. Actually, looking at the syslogd man page, it says it can receive messages over such a socket - but points out a possible security problem (although this could probably be avoided). -- James Raynard, Edinburgh, Scotland jraynard@dial.pipex.com james@jraynard.demon.co.uk
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199605172053.UAA27032>