Bill Cole wrote:
> You might even be better off configuring your system to not use the
> TSC as a clock source. There's a strong chance that you won't really
> be sacrificing anything that you actually use.
Time to conclude on this.
Rather than going along with my Dovecot hack, I went and change
Bill Cole wrote:
> At 11:10 AM +0200 6/20/08, Anders wrote:
>>By that line, the entire "time moved backwards" thing does not belong
>>in Dovecot.
>
> I suspect that you don't understand why that is in Dovecot. Timo has
> explained it in detail a few times, but the bottom line is simple:
> running
At 11:10 AM +0200 6/20/08, Anders wrote:
Johannes Berg <[EMAIL PROTECTED]> writes:
On Fri, 2008-06-20 at 10:53 +0200, Anders wrote:
I was puzzled that it was always 4398 seconds, in particular because
this server runs an NTP daemon. A little searching for this problem
shows that it is an
> This bug causes Dovecot to run the IO loop in the future for one
> iteration, and then die when we get back to present time.
>
> By the time Dovecot dies, some damage could already have happend, for
> example if ioloop_time is stored to permanent storage.
Hmm, ok, I was under the impression
Johannes Berg wrote:
On Fri, 2008-06-20 at 11:10 +0200, Anders wrote:
Johannes Berg <[EMAIL PROTECTED]> writes:
On Fri, 2008-06-20 at 10:53 +0200, Anders wrote:
I was puzzled that it was always 4398 seconds, in particular because
this server runs an NTP daemon. A little searching for this pro
On Fri, 2008-06-20 at 11:10 +0200, Anders wrote:
> Johannes Berg <[EMAIL PROTECTED]> writes:
>
> > On Fri, 2008-06-20 at 10:53 +0200, Anders wrote:
> >>
> >> I was puzzled that it was always 4398 seconds, in particular because
> >> this server runs an NTP daemon. A little searching for this proble
On Fri, 2008-06-20 at 10:53 +0200, Anders wrote:
> Dovecot (v1.1.rc8) died tonight, with an error about time moving
> backwards by 4398 seconds. I can see from logs that this has happend a
> few times before with the imap processes, without me noticing. I sure
> noticed the master process missing,
Johannes Berg <[EMAIL PROTECTED]> writes:
> On Fri, 2008-06-20 at 10:53 +0200, Anders wrote:
>>
>> I was puzzled that it was always 4398 seconds, in particular because
>> this server runs an NTP daemon. A little searching for this problem
>> shows that it is an issue with the Linux kernel gettimeo
On Fri, 2008-06-20 at 10:53 +0200, Anders wrote:
> Dovecot (v1.1.rc8) died tonight, with an error about time moving
> backwards by 4398 seconds. I can see from logs that this has happend a
> few times before with the imap processes, without me noticing. I sure
> noticed the master process missing,
Dovecot (v1.1.rc8) died tonight, with an error about time moving
backwards by 4398 seconds. I can see from logs that this has happend a
few times before with the imap processes, without me noticing. I sure
noticed the master process missing, though :-).
I was puzzled that it was always 4398 second
10 matches
Mail list logo
