notify
michab
iniquity at gmx.de
Fri Nov 3 01:48:02 UTC 2000
am i right, that when i want the NS to reload a new entered zone=
that
i have to enter the following ??
ndc reconfig
ndc reload [zone]
??? thx....
Jim Reid (jim at rfc1035.com) schrieb:
>>>>>> "Andreas" =3D=3D Andreas Gietl <gietl at gietl.com> writes:
>
> Andreas> is there nothing in the ndc that has the same effect
>than
> Andreas> a SIGHUP?
>
>Maybe. But what effect does SIGHUP have and how can anyone be
certain
>that this signal always has the same effect on all versions of=
BIND?
>
>Just use ndc and its far richer command set. Managing processes=
by
>sending signals to them is crude, clumsy and limiting. For=
example,
>if
>all that's changed is one zone file or a statement in=
named.conf
>forcing a global reload of everything - stat()ing every master=
zone
>file and SOA checking every slave zone - by sending the name=
server
>SIGHUP is ridiculous overkill. With ndc, you could just do an
>incremental reload ("ndc reload changed-zone-name") or you could=
get
>the name server to re-read named.conf by typing "ndc reconfig".=
This
>is
>a Big Win, especially on name servers that have lots of zones.=
Oh
and
>the UID running ndc doesn't have to be the same as the UID tht=
runs
>the name server. That flexibility does not exist with signals.
-- michab, iniquity at gmx.de on 11.03.2000
More information about the bind-users
mailing list