From owner-freebsd-isp Sun Oct 15 9:30:25 2000 Delivered-To: freebsd-isp@freebsd.org Received: from misery.sdf.com (misery.sdf.com [204.244.213.49]) by hub.freebsd.org (Postfix) with ESMTP id 29ECB37B66E for ; Sun, 15 Oct 2000 09:30:23 -0700 (PDT) Received: from tom (helo=localhost) by misery.sdf.com with local-esmtp (Exim 2.12 #1) id 13kqIc-0006yO-00; Sun, 15 Oct 2000 09:06:10 -0700 Date: Sun, 15 Oct 2000 09:06:08 -0700 (PDT) From: Tom Samplonius To: "Thomas Krause, CI" Cc: freebsd-isp@freebsd.org Subject: Re: running bind -u bind -g bind In-Reply-To: <4.3.2.7.0.20001015092357.0290b0a0@wallace.webmatic.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, 15 Oct 2000, Thomas Krause, CI wrote: > And after a 'named.restart', named is running as root: > > root@kraxon:/ # named.restart > new pid is 230 > root@kraxon:/ # ps axw | grep named > 230 ?? Ss 0:00.09 /usr/sbin/named ... > Any Ideas, how to reload the named? > I'm using FreeBSD 4.1.1-R First of all, reload and restart are very different things. named.reload triggers are reload where named reloads all the zone file. named.restart actually kills the named process, dumps the cache, and then starts up named again. It seems the named.restart script starts named up without the paramters that request that it run as the "bind" user. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message