In message <2971f259-4897-48f8-b418-2f7599075...@gronkulator.com>, Rich Goodson
writes:
> The behavior of 'rndc halt -p' appears to be different from the =20
> documentation.
>
> According to the BIND 9.4 ARM rndc section:
> halt [-p] Stop the server immediately. Recent changes made through =20
> dynamic update or IXFR
> are not saved to the master =EF=AC=81les, but will be rolled forward =
> from the =20
> journal =EF=AC=81les when the
> server is restarted. If -p is speci=EF=AC=81ed named=E2=80=99s process =
> id is =20
> returned. This allows an external
> process to determine when named had completed halting.
>
> But the actual behavior seems to be that 'rndc halt -p' returns =20
> immediately with the PID of named, but a 'ps -ef' shows named still =20
> running until it's done answering its unfinished recursive queries (or =20=
>
> whatever it's busy doing).
>
> Is rndc broken, or is the documentation wrong, or am I missing =20
> something?
>
> If it makes a difference, this is on a server that exclusively does =20
> recursive resolution and does not serve any authoritative zones.
>
> -rich
named is just freeing all memory that it has allocated. If there
has been a memory leak this is when it will be detected.
Mark
--
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: mark_andr...@isc.org
_______________________________________________
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
