From owner-freebsd-isp  Tue May  6 18:51:08 1997
Return-Path: <owner-isp>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id SAA20955
          for isp-outgoing; Tue, 6 May 1997 18:51:08 -0700 (PDT)
Received: from irbs.irbs.com (jc@irbs.irbs.com [199.182.75.129])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA20949
          for <freebsd-isp@FreeBSD.ORG>; Tue, 6 May 1997 18:51:02 -0700 (PDT)
Received: (from jc@localhost)
	by irbs.irbs.com (8.8.5/8.8.5) id VAA13454;
	Tue, 6 May 1997 21:50:37 -0400 (EDT)
Message-ID: <19970506215037.34284@irbs.com>
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.
References: <Pine.BSF.3.95q.970505213619.10297A-100000@wopr.inetu.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.69
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
X-Organization: IRBS Engineering, (954) 792-9551
Sender: owner-isp@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

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