Quoth Alex on Tue, Jan 23, 2007 at 05:56:42AM -0800: > I think the clue in the log is that I made the change on the 19th. > I discovered that the service was enabled on the 21st. So if I read > the log messages correctly, its state went like this; > > restart->:kill->disabled > > I've seen similar behavior in the past, where the DNS server would be > considered "disabled" after a reboot when the service was very much > "enabled" during the previous boot.
Yes, originally named interpreted the stop method as a disable signal from rndc, I think, so it then proceeded to disable itself. I think that has been fixed, but I don't know when. David
