Bug 26488

Summary: incomplete named sandbox information
Product: Base System Reporter: dpelleg+bsd <dpelleg+bsd>
Component: confAssignee: Doug Barton <dougb>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: Unspecified   
Hardware: Any   
OS: Any   
Attachments:
Description Flags
file.diff none

Description dpelleg+bsd 2001-04-10 19:40:01 UTC 
The sandbox sequence described in /etc/namedb/named.conf is not likely
to result in a working configuration. Further, neither logging nor ndc control
will work for it.

How-To-Repeat: less /etc/namedb/named.conf
Comment 1 dwmalone 2001-04-15 14:13:59 UTC 
> The sandbox sequence described in /etc/namedb/named.conf is not likely
> to result in a working configuration. Further, neither logging nor ndc control
> will work for it.

We use bind in almost exactly the configuration you mention, though
I also make a symlink for the pid file too. I note, however, that
syslogging works fine in this setup (since syslog(3) doesn't write
files directly but sends messages via the socket /var/run/log to
syslogd).

Other than that the change looks like a good idea.

	David.
Comment 2 Doug Barton freebsd_committer freebsd_triage 2002-07-01 03:01:49 UTC 
Responsible Changed
From-To: freebsd-bugs->dougb


Borrow this so I don't forget about it.
Comment 3 Doug Barton freebsd_committer freebsd_triage 2004-11-28 12:36:38 UTC 
State Changed
From-To: open->feedback


Does the new named chroot configuration in 6-current 
and RELENG_5 meet your needs?
Comment 4 Doug Barton freebsd_committer freebsd_triage 2004-12-13 18:38:31 UTC 
State Changed
From-To: feedback->closed


Originator reported on 28 November in private mail that it is 
OK to close this PR.