[488] in testers
Re: rt 6.4A: named, named(8)
daemon@ATHENA.MIT.EDU (daemon@ATHENA.MIT.EDU)
Thu Dec 14 18:11:45 1989
From: probe@ATHENA.MIT.EDU
Date: Thu, 14 Dec 89 18:11:20 -0500
To: jik@PIT-MANAGER.MIT.EDU
Cc: testers@ATHENA.MIT.EDU
In-Reply-To: Jonathan I. Kamens's message of Thu, 14 Dec 89 18:04:44 -0500,
Reply-To: Richard Basch <probe@ATHENA.MIT.EDU>
Date: Thu, 14 Dec 89 18:04:44 -0500
From: Jonathan I. Kamens <jik@PIT-MANAGER.MIT.EDU>
Sender: jik@PIT-MANAGER.MIT.EDU
From: probe@ATHENA.MIT.EDU
Date: Thu, 14 Dec 89 17:59:35 -0500
Reply-To: Richard Basch <probe@ATHENA.MIT.EDU>
Address: 1 Amherst St., E40-342C, Cambridge, MA 02139
Phone: (617) 225-6355
Did you kill off named? kill -HUP `cat /etc/named.pid` is NOT
sufficient. You must kill it and restart it.
Why? This, too, is not the same behavior as the old named, and is
not (as far as I could tell, although I certainly could have missed
it) documented in named(8), which says that SIGHUP "Causes server to
read named.boot and reload database."
jik
Actually, "kill -HUP" has never really worked properly. The problem
this time is that your cache still has various entries listed and the
TTL has not yet expired. This is why it concatenated the information.
The man-page never claims that it flushes the database when you send it
a SIGHUP, though I admit, it is ambiguous given a familiarity with the
previous behavior.
-Richard
