On Tue, 06 Dec 2005, Florian Weimer wrote:
> Technically, the BIND code is wrong because pthread_cond_timedwait is
What else is new... :(
> not guaranteed to return within 15 seconds after the requested
> timeout. But if this happens without extremely high load, something
> fishy is going on.
I
* Marc Haber:
> May I ask why you pollute the general development mailing list for
> that?
The comment in the code is:
/*
* This is a temporary (probably) hack to fix a bug on tru64 5.1
* and 5.1a. Sometimes, pthread_cond_timedwait() doesn't actually
* return
On Mon, 5 Dec 2005 15:50:05 +0100, Klaus Ethgen <[EMAIL PROTECTED]>
wrote:
>With newer upgrade of bind9 I get the Message "*** POKED TIMER ***" in
>the log several times. I'm not sure if this is a bug or just
>logpolution.
>
>Do anybody know about this issue and why it happens?
May I ask why you p
3 matches
Mail list logo