From owner-freebsd-bugs Wed Oct 18 20:33:32 2000 Delivered-To: freebsd-bugs@freebsd.org Received: from elvis.mu.org (elvis.mu.org [207.154.226.10]) by hub.freebsd.org (Postfix) with ESMTP id 33B8837B479 for ; Wed, 18 Oct 2000 20:33:31 -0700 (PDT) Received: by elvis.mu.org (Postfix, from userid 1061) id B8B4C2B2BD; Wed, 18 Oct 2000 22:33:25 -0500 (CDT) Date: Wed, 18 Oct 2000 22:33:25 -0500 From: David Drum 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> Mail-Followup-To: David Drum , freebsd-bugs@FreeBSD.org References: <20001017081857.C46425@elvis.mu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from DougB@gorean.org on Tue, Oct 17, 2000 at 12:52:29PM -0700 Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org 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