POKED TIMER

2006-12-07 Thread Robert Fitzpatrick
I get this message in the logs from named on a machine running FreeBSD 5.4 and BIND 9.3.1. From what I have found out, there may be a problem with this mix... http://unix.derkeiler.com/Mailing-Lists/FreeBSD/stable/2005-06/1035.html This post suggests an option to get the ports system to

Re: *** POKED TIMER *** in named

2005-08-15 Thread Kris Kennaway
]: starting BIND 9.3.1 Aug 15 09:26:15 www named[769]: couldn't add command channel 127.0.0.1#953: not found Aug 15 09:26:15 www named[769]: couldn't add command channel ::1#953: not found Aug 15 09:26:15 www named[769]: running Aug 15 09:27:34 www named[769]: *** POKED TIMER *** Is there any

*** POKED TIMER *** in named

2005-08-14 Thread DeadMan Xia ....
channel 127.0.0.1#953: not found Aug 15 09:26:15 www named[769]: couldn't add command channel ::1#953: not found Aug 15 09:26:15 www named[769]: running Aug 15 09:27:34 www named[769]: *** POKED TIMER *** Is there any one who can help me out, so that i may get rid of this trouble, Thanx in Advance

named[604]: *** POKED TIMER ***

2005-01-20 Thread Martin Zibert
Greetings.. I am running FreeBSD 5.3 on dual Xeon 3GHz box and today i got a line in my messages, which goes: named[604]: *** POKED TIMER *** I've searched the web but i could not find what this means. Could anyone help me? Is this a bug? Thanks in advance. Martin

Re: named[604]: *** POKED TIMER ***

2005-01-20 Thread Kris Kennaway
On Thu, Jan 20, 2005 at 06:39:21PM +0100, Martin Zibert wrote: Greetings.. I am running FreeBSD 5.3 on dual Xeon 3GHz box and today i got a line in my messages, which goes: named[604]: *** POKED TIMER *** I've searched the web but i could not find what this means. Could anyone help me

named logging: POKED TIMER

2004-11-11 Thread Rob
Hi, With 5.3, running named (cashing nameserver only) and ntpd to sync the time, I see in /var/log/messages about twice a day a line like this: Nov 11 05:41:44 para named[356]: *** POKED TIMER *** Nov 11 14:51:09 para named[355]: *** POKED TIMER *** What does this mean? Is it still a bug