From owner-freebsd-security  Tue May 16 10:51: 9 2000
Delivered-To: freebsd-security@freebsd.org
Received: from sivka.rdy.com (sivka.rdy.com [207.33.166.86])
	by hub.freebsd.org (Postfix) with ESMTP id 48FF337B784
	for <freebsd-security@FreeBSD.ORG>; Tue, 16 May 2000 10:50:45 -0700 (PDT)
	(envelope-from dima@rdy.com)
Received: (from dima@localhost)
	by sivka.rdy.com (8.9.3/8.9.3) id KAA71328;
	Tue, 16 May 2000 10:50:09 -0700 (PDT)
	(envelope-from dima)
Message-Id: <200005161750.KAA71328@sivka.rdy.com>
Subject: Re: pid file for named
In-Reply-To: <Pine.BSF.4.21.0005160634430.21765-100000@srh0902.urh.uiuc.edu>
 from Frank Tobin at "May 16, 2000 06:48:05 am"
To: Frank Tobin <ftobin@uiuc.edu>
Date: Tue, 16 May 2000 10:50:09 -0700 (PDT)
Cc: FreeBSD-security Mailing List <freebsd-security@FreeBSD.ORG>
Organization: HackerDome
Reply-To: dima@rdy.com
From: dima@rdy.com (Dima Ruban)
X-Mailer: ELM [version 2.4ME+ PL68 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-security@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Frank Tobin writes:
> One often wishes to run daemons such as named under other users, e.g.,
> bind:bind.  In order to allow bind to write out zones and associated fun
> stuff correctly, one then does a
> 
> chmod -R bind:bind /etc/named
> 
> However, the pid file, /var/run/named.pid, which named tries to write out

You can set it in named.conf:

options {
	...
	pid-file "/etc/namedb/run/named.pid";
	...
};


However, this will break "ncd", since it's looking for /var/run/named.pid
instead of extracting current "pid-file" value from the named.conf.


-- dima


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-security" in the body of the message