2010 09:49
To: Ondrej Zajicek
Cc: Bird Users
Subject: Re: another bug: system time change
On Apr 9, 2010, at 10:49 , Ondrej Zajicek wrote:
> On Fri, Apr 09, 2010 at 10:22:05AM +0200, Wolfgang Hennerbichler wrote:
>> Hi Ondrejs,
>>
>> I think I found another bug. For some my
On Apr 9, 2010, at 14:08 , Ondrej Zajicek wrote:
> On Fri, Apr 09, 2010 at 10:49:15AM +0200, Wolfgang Hennerbichler wrote:
>> Hm. Now this is strange indeed. I run linux 2.6.33.1 (amd64) - but it
>> is a virtualized host (with xen). Maybe it was xen's fault, but the logs
>> don't reveal much as y
On Fri, Apr 09, 2010 at 10:49:15AM +0200, Wolfgang Hennerbichler wrote:
> Hm. Now this is strange indeed. I run linux 2.6.33.1 (amd64) - but it
> is a virtualized host (with xen). Maybe it was xen's fault, but the logs
> don't reveal much as you see. Hm. this sucks.
If there is a virtualization i
On Apr 9, 2010, at 12:44 , Arnold Nipper wrote:
>
> Is this really a BIRD bug? I guess it is expected behaviour to drop a
> session if you _think_ you missed keepalives
Time Counters within a Daemon should NEVER be dependent on the system time, so
yes, I would consider this a bug of BIRD, but i
On 09.04.2010 10:22 Wolfgang Hennerbichler wrote
> Hi Ondrejs,
>
> I think I found another bug. For some mysterious reason our system time
> jumped forward (more than 30.000 seconds) on one of our route-servers. I
> don't know why this happened, but I suspect a broken ntp server could have
>
On Apr 9, 2010, at 10:49 , Ondrej Zajicek wrote:
> On Fri, Apr 09, 2010 at 10:22:05AM +0200, Wolfgang Hennerbichler wrote:
>> Hi Ondrejs,
>>
>> I think I found another bug. For some mysterious reason our system time
>> jumped forward (more than 30.000 seconds) on one of our route-servers. I
>
On Fri, Apr 09, 2010 at 10:22:05AM +0200, Wolfgang Hennerbichler wrote:
> Hi Ondrejs,
>
> I think I found another bug. For some mysterious reason our system time
> jumped forward (more than 30.000 seconds) on one of our route-servers. I
> don't know why this happened, but I suspect a broken ntp
Hi Ondrejs,
I think I found another bug. For some mysterious reason our system time jumped
forward (more than 30.000 seconds) on one of our route-servers. I don't know
why this happened, but I suspect a broken ntp server could have caused this.
Nevetheless, this was reason enough for BIRD to d
