[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- To: tech_(_at_)_openbsd_(_dot_)_org
- Subject: Re: /var/named
- From: Simon Dick <simond_(_at_)_bessie_(_dot_)_mojo_(_dot_)_org>
- Date: Wed, 3 Jun 1998 15:18:26 +0100 (BST)
- Delivery-date: Wed Jun 3 07:22:04 1998
- Reply-to: tech_(_at_)_openbsd_(_dot_)_org
> On Wed, 3 Jun 1998, Todd T. Fries wrote:
> > > Couldn't it read /etc/named.boot, and chroot to whatever directory
> > > is specified there??
> > .. and when you did a 'kill -HUP <pid>' it would be able to re-read it how?
> I usually advice against sighup'ing named. Thats what the ndc
> restart/reload command is for, no?
> As long as ndc knew where things were at, all would be well.
> I haven't used bind under OpenBSD yet, so I don't know how big a problem
> this is, though I routinely move db files around I am very used to
> /etc/named.conf being there.
Stopping and restarting is OK as long as you don't serve too many
domains, otherwise it saves a *lot* of time just HUPing named.
Simon Dick simond_(_at_)_bessie_(_dot_)_mojo_(_dot_)_org
Visit your host, monkey.org