From owner-freebsd-questions Fri May 17 16:51:02 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA01681 for questions-outgoing; Fri, 17 May 1996 16:51:02 -0700 (PDT) Received: from relay-4.mail.demon.net (relay-4.mail.demon.net [158.152.1.108]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id QAA01676 for ; Fri, 17 May 1996 16:50:59 -0700 (PDT) Received: from post.demon.co.uk ([158.152.1.72]) by relay-4.mail.demon.net id aa24363; 17 May 96 23:40 GMT Received: from jraynard.demon.co.uk ([158.152.42.77]) by relay-3.mail.demon.net id aa17190; 18 May 96 0:40 +0100 Received: (from fqueries@localhost) by jraynard.demon.co.uk (8.7.5/8.6.12) id UAA27032; Fri, 17 May 1996 20:53:47 GMT Date: Fri, 17 May 1996 20:53:47 GMT From: James Raynard Message-Id: <199605172053.UAA27032@jraynard.demon.co.uk> To: patl@phoenix.volant.org CC: freebsd-questions@freebsd.org In-reply-to: <9605161608.AA23936@asimov.volant.org> (patl@asimov.volant.org) Subject: Re: Syslog -vs- chroot Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > 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