Date: Wed, 18 Oct 2000 22:33:25 -0500 From: David Drum <david@mu.org> To: freebsd-bugs@FreeBSD.org Subject: Re: conf/22038: Default location of named.pid file assumes named is running as root Message-ID: <20001018223325.A83999@elvis.mu.org> In-Reply-To: <Pine.BSF.4.21.0010171248550.16517-100000@dt051n37.san.rr.com>; from DougB@gorean.org on Tue, Oct 17, 2000 at 12:52:29PM -0700 References: <20001017081857.C46425@elvis.mu.org> <Pine.BSF.4.21.0010171248550.16517-100000@dt051n37.san.rr.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Quoth Doug Barton: > This isn't a freebsd issue, it's a BIND issue. People who > don't have a sufficient amount of knowledge about how BIND works to > run it successfully as an unpriviliged user won't be helped by your > suggestion. It will just be some other aspect of BIND configuration > that trips them up. I suppose it can be argued that someone who is essentially ignorant about BIND, at least enough not to know about the side effects on the PID file of running "-u bind", will not be running "ndc reload" either. Perhaps I should suggest to the BIND maintainers that it spit out a message at startup if the parent directory of the PID file is not writable by the user specified by the "-u". It is probably appropriate to close this PR. Regards, David Drum david@mu.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20001018223325.A83999>