From owner-freebsd-questions Thu Sep 6 15: 7:35 2001 Delivered-To: freebsd-questions@freebsd.org Received: from stargate.clickcom.com (stargate.clickcom.com [209.198.22.4]) by hub.freebsd.org (Postfix) with ESMTP id 0B92E37B403 for ; Thu, 6 Sep 2001 15:07:30 -0700 (PDT) Received: from fishbowl (dhcp-1.clt.clickcom.com [209.198.22.65]) by stargate.clickcom.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21) id SM465NSR; Thu, 6 Sep 2001 18:07:35 -0400 Reply-To: From: "John Straiton" To: "Andrew Eross" , Subject: RE: named chroot trouble Date: Thu, 6 Sep 2001 18:06:33 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Importance: Normal In-Reply-To: <008101c1371c$8fb57390$8e45b184@eross> Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Once chrooted, named can no longer write to syslog like it used to because it can not get to /dev/log (outside the chroot). You have to tell syslogd to place a pointer within the chroot that named can write to. If your chroot is in /etc/namedb/ then you need to mkdir /etc/namedb/dev then add syslogd_flags="-l /etc/namedb/dev/log" to your rc.conf restart syslogd with those flags and you'll find that there's now a /etc/namedb/dev/log filehandle there. named will write to this and work fine. Chrooting BIND9: http://profile.sh/bsdwiki/index.php?Setting%20up%20secure%20DNS%20servers%20 with%20BIND%20under%20FreeBSD Chrooting BIND8: http://www.psionic.com/papers/dns/dns-openbsd John Straiton -----Original Message----- From: owner-freebsd-questions@FreeBSD.ORG [mailto:owner-freebsd-questions@FreeBSD.ORG]On Behalf Of Andrew Eross Sent: Thursday, September 06, 2001 5:41 PM To: questions@freebsd.org Subject: named chroot trouble Hi, I run named chroot'd on my machine, but I noticed that since it runs chroot'd it no longer reports to syslog ... Is there anything that I can do about this? Thanks, Andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message