I did leave a little almost on-purpose dangling hint that got me
an off-list query... Since I'm replying, I might as well reply
on-list for the record, even if this is getting off-topic. I've
just about exhausted my knowledge on the subject, so further
questions will probably find a more attentive
On 5/6/2011 5:53 AM, Charles Marcus wrote:
ntpdate, which causes large jumps, should only be used at
boot time
BEFORE server processes are started, then ntp CLIENT keeps the systems
clock in sync using tiny increments, usually less than a second.
No, ntpd adjusts the clock frequency to keep t
On Fri, 06 May 2011 06:53:13 -0400
Charles Marcus articulated:
> On 2011-05-06 12:05 AM, Frank Bonnet wrote:
> > Le 05/05/2011 20:49, Timo Sirainen a écrit :
> >> On 5.5.2011, at 20.45, Spyros Tsiolis wrote:
> >>> AFAIK, to keep good time on a linux machine inside the network,
> >>> you need to r
On 2011-05-06 12:05 AM, Frank Bonnet wrote:
> Le 05/05/2011 20:49, Timo Sirainen a écrit :
>> On 5.5.2011, at 20.45, Spyros Tsiolis wrote:
>>> AFAIK, to keep good time on a linux machine inside the network,
>>> you need to run "ntpdate" and not "ntpd".
>> No no no! That just makes things worse! It
Are you got this warnings only after OS reboot?
--
Alexander Moisseev
Le 05/05/2011 20:49, Timo Sirainen a écrit :
On 5.5.2011, at 20.45, Spyros Tsiolis wrote:
AFAIK, to keep good time on a linux machine inside the network,
you need to run "ntpdate" and not "ntpd".
No no no! That just makes things worse! It's the most common reason for these "Time
jumped for
On Thu, 5 May 2011 23:43:25 +0200
Lorens Kockum articulated:
> On Thu, May 05, 2011 at 07:54:50PM +0100, Spyros Tsiolis wrote:
> >
> > Seriously ?
>
> Yes, Timo was (of course) both serious and correct.
>
> ntpdate takes one or more NTP servers as parameters, and sets
> your server's time to m
On Thu, May 05, 2011 at 07:54:50PM +0100, Spyros Tsiolis wrote:
>
> Seriously ?
Yes, Timo was (of course) both serious and correct.
ntpdate takes one or more NTP servers as parameters, and sets
your server's time to match that of the NTP servers. That may
well cause a jump, even a massive jump.
Le 05/05/2011 à 21:27, Rick Romero a écrit :
I thought everyone knew that if you removed the 1.55v watch battery from
the motherboard, you could put in a 1.6v battery and time will run
faster. Then just use ntpdate - time will never jump forward, and
dovecot won't crash.
:D
Hi,
As Timo just
, Spyros Tsiolis wrote:
--- On Thu, 5/5/11, Timo Sirainen wrote:
From: Timo Sirainen
Subject: Re: [Dovecot] May 05 07:20:21 imap: Warning: Time jumped
forwards 16 seconds
To: "Spyros Tsiolis"
Cc: f.bon...@esiee.fr, "Dovecot"
Date: Thursday, 5 May, 2011, 21:49
On 5.5.2011, at 2
Quoting Noel :
On 5/5/2011 1:54 PM, Spyros Tsiolis wrote:
--- On Thu, 5/5/11, Timo Sirainen wrote:
From: Timo Sirainen
Subject: Re: [Dovecot] May 05 07:20:21 imap: Warning: Time jumped
forwards 16 seconds
To: "Spyros Tsiolis"
Cc: f.bon...@esiee.fr, "Dovecot"
Date: T
On 5/5/2011 1:54 PM, Spyros Tsiolis wrote:
--- On Thu, 5/5/11, Timo Sirainen wrote:
From: Timo Sirainen
Subject: Re: [Dovecot] May 05 07:20:21 imap: Warning: Time jumped forwards 16
seconds
To: "Spyros Tsiolis"
Cc: f.bon...@esiee.fr, "Dovecot"
Date: Thursday, 5 May, 201
--- On Thu, 5/5/11, Timo Sirainen wrote:
> From: Timo Sirainen
> Subject: Re: [Dovecot] May 05 07:20:21 imap: Warning: Time jumped forwards 16
> seconds
> To: "Spyros Tsiolis"
> Cc: f.bon...@esiee.fr, "Dovecot"
> Date: Thursday, 5 May, 2011, 21:49
&
On 5.5.2011, at 20.45, Spyros Tsiolis wrote:
> AFAIK, to keep good time on a linux machine inside the network,
> you need to run "ntpdate" and not "ntpd".
No no no! That just makes things worse! It's the most common reason for these
"Time jumped forwards/backwards" warnings.
Hello,
You say ntpd is running.
Is it running as a daemon ?
AFAIK, to keep good time on a linux machine inside the network,
you need to run "ntpdate" and not "ntpd".
I had _exactly_ the same problem and I was running an ntp daemon.
I wasn't actually syncing to anything.
So,I did some searching
ntp isn't a magical fix.
You need a good selection of source servers, or local time sources for
it to pick a steady reliable time to use.
Also, if the clock in your computer drifts too much, ntp will refuse
to correct it or keep it in sync at all.
Quoting Frank Bonnet :
Hello
I get th
On 2011-05-05 1:25 AM, Frank Bonnet wrote:
> Hello
>
> I get this warning in dovecot.log
>
> the machine is running ntpd so this is
> a bit strange ...
How are you using it? It obviously isn't working correctly if your
server isn't staying in time.
--
Best regards,
Charles
Hello
I get this warning in dovecot.log
the machine is running ntpd so this is
a bit strange ...
18 matches
Mail list logo
