Timo Sirainen wrote:
http://wiki.dovecot.org/TimeMovedBackwards bottom answers this. A
restart isn't much better than just ignoring the time change.
In point 3 (you can use clockspeed as well) you could mention
chrony, too:
http://chrony.sunsite.dk/
Thank you,
Arno
Matthijs Kooijman wrote:
but I think it's not so trivial to handle this properly, without risking data
loss (as Timo pointed out, immediately restarting is not really helping, since
you'll still be running in the past.
It would be interesting (as I do not know anything about the dovecot
Hi Arno,
http://wiki.dovecot.org/TimeMovedBackwards bottom answers this. A
restart isn't much better than just ignoring the time change.
In point 3 (you can use clockspeed as well) you could mention
chrony, too:
That page has an edit button, so feel free!
Gr.
Matthijs
signature.asc
On 6/9/2009, Eugene (ge...@geniechka.ru) wrote:
Basically it is the only thing I don't like in Dovecot... and was
even planning to hack the time check out of the code =))
That would not be a good idea.
You are chasing a symptom (the way dovecot responds to a serious
problem), instead of the
On 6/10/2009, Arno Wald (arno.w...@netcologne.de) wrote:
Why is the time that the mail server is running in important for this
management?
No offense, but are you serious? If so, I certainly hope you aren't
running a public mail server.
--
Best regards,
Charles
Matthijs Kooijman wrote:
In point 3 (you can use clockspeed as well) you could mention
chrony, too:
That page has an edit button, so feel free!
Done. I hope I have not destroyed anything.
Bye, Arno.
Charles Marcus wrote:
On 6/10/2009, Arno Wald (arno.w...@netcologne.de) wrote:
Why is the time that the mail server is running in important for this
management?
No offense, but are you serious?
Well, I really meant the question seriously. A server gets mails, stores
them and delivers them
Backward time steps can cause real problems for Maildir, as its
uniqueness algorithms can be ... theoretically correct.
H
On Wed, Jun 10, 2009 at 01:01:28AM +0400, Eugene wrote:
Hello
From: Timo Sirainen t...@iki.fi
But really, all this leads is that admin has to detect the dovecot
termination and simply go and restart it manually -- after some bad
thoughts.
Or the admin actually permanently fixes the
Timo Sirainen wrote:
Hmm. I suppose I could change Dovecot master so that if no imap/pop3
processes have been created yet, it would silently ignore the clock move.
Also it might be an idea to just restart dovecot instead of completely
stopping it. If this happens to often in a certain time
On Jun 8, 2009, at 11:40 PM, Arno Wald wrote:
Timo Sirainen wrote:
Hmm. I suppose I could change Dovecot master so that if no imap/
pop3 processes have been created yet, it would silently ignore the
clock move.
Also it might be an idea to just restart dovecot instead of
completely
NTP comes with a script, ntp-wait, that is specifically designed to be
used during the boot-sequence for the purpose of waiting until the clock
is sync'd before starting time-sensitive applications.
See http://support.ntp.org/bin/view/Support/StartingNTP4 for more
information.
BCP is:
- Start
Hi Timo,
Date: Tue, 9 Jun 2009 09:40:20 -0700
From: Timo Sirainen t...@iki.fi
On Jun 8, 2009, at 11:40 PM, Arno Wald wrote:
Timo Sirainen wrote:
Hmm. I suppose I could change Dovecot master so that if no imap/
pop3 processes have been created yet, it would silently ignore the
clock move.
On Jun 9, 2009, at 1:03 PM, Eugene wrote:
But really, all this leads is that admin has to detect the dovecot
termination and simply go and restart it manually -- after some bad
thoughts.
Or the admin actually permanently fixes the time.
Timo wrote:
On Jun 9, 2009, at 1:03 PM, Eugene wrote:
But really, all this leads is that admin has to detect the dovecot
termination and simply go and restart it manually -- after some bad
thoughts.
Or the admin actually permanently fixes the time.
This is usually a startup issue
Hi Eugene,
But really, all this leads is that admin has to detect the dovecot
termination and simply go and restart it manually -- after some bad
thoughts.
During normal operation, on 99% of the hosts, the clock should never need to
leap backwards. So if that ever happens, it seems fine
Hello
From: Timo Sirainen t...@iki.fi
But really, all this leads is that admin has to detect the dovecot
termination and simply go and restart it manually -- after some bad
thoughts.
Or the admin actually permanently fixes the time.
In most cases we talk about, it can't be fixed permanently
On Jun 9, 2009, at 1:54 PM, Harlan Stenn wrote:
Timo wrote:
On Jun 9, 2009, at 1:03 PM, Eugene wrote:
But really, all this leads is that admin has to detect the dovecot
termination and simply go and restart it manually -- after some bad
thoughts.
Or the admin actually permanently fixes the
Eugene wrote:
In most cases we talk about, it can't be fixed permanently because this
happens after (cold or warm) system restart, when ntpd can take up to 15
minutes (and in most cases about 3-5 minutes) to actually resync the time.
If you have a good drift file and use iburst (as discussed
I have been running AIX, IBM's Unix on IBM hardware for years but am
being forced into Lintel, mostly because of IBM hollowing out support,
moving to a Fortune 500 only customer base and leaving the small shop
increasingly SOL. One of the realities of Lintel is that the hardware
is, compared
on 6-6-2009 12:52 PM Arno Wald spake the following:
Pascal Volk wrote:
On Debian systems I'm very happy with the OpenBSD NTP daemon.
Package: openntpd
This ntpd adjusts the local time in little steps.
Also on startup? ntpd uses little steps while running, too. But only at
startup it seems
on 6-6-2009 11:50 AM Scott Haneda spake the following:
Sorry for the top post and lack of snipping this email down, I'm using a
mobile phone.
Can you explain why the system clock gets so far out of time? I
certainly struggle with crime (time?) drifting even on an always network
connected
on 6-6-2009 2:45 PM Harlan Stenn spake the following:
Juergen wrote:
Harlan wrote:
There is no corrected version of the real-time clock before the PC goes
online.
I'd suggest to read chrony's manual. Chrony stores the reference values
collected while running online for further use after
On Jun 8, 2009, at 11:28 AM, Scott Silva wrote:
Many startup scripts for ntp make a call to ntpdate or an equivalent
to get
the time close on startup, then call ntp to keep the clock synced.
Hmm. I suppose I could change Dovecot master so that if no imap/pop3
processes have been created
Arno Wald wrote:
Is there a more elegant way to use dovecot and ntpd on a manually dialed
in PC?
2 things might help: 1, run ntpd in cron every 10 minutes or so.
That should avoid the startup issue. 2, sync your hardware
clock every time. That should keep your clock closer to
accurate.
You
On Jun 6, 2009, at 11:19 AM, Arno Wald wrote:
My idea now is to not start ntpd on system boot, but only on if-up.
But this brings up the same fatal error of dovecot as ntpd seems to
hardly set the time, too. The only idea I have left is to stop
dovecot, start ntpd and then start dovecot
Scott Haneda wrote:
Can you explain why the system clock gets so far out of time?
No, I cannot, I do not know. Is it possible that the clock is out of order?
I did compare the times with another PC that is ntpd controlled. And
after 1 hour the times differ for 1 second again. It seems that
Timo Sirainen wrote:
Wonder if http://cr.yp.to/clockspeed.html would work better than ntpd?
This is interesting, thank you. I will give it a try if ntpd or ntpdate
will be no solution for me. But as there is no package for this in
debian I would like to use the ntp stuff instead first.
John Gateley wrote:
2 things might help:
Thank you for your suggestions. This reminded me of an ntpdate option:
ntpdate can be configured to change the time not in a big step on
startup by using the option
-B
Force the time to always be slewed using the adjtime() system call,
even if the
Have you seen http://support.ntp.org/Support ?
You said your clock is running fast, so it's not a clock interrupt
issue.
If your OS supports it, and you have a *steady* problem with your clock,
you might be able to correct this problem with the tickadj program and
then ntpd should be able to
On 06/06/2009 09:22 PM Arno Wald wrote:
This is interesting, thank you. I will give it a try if ntpd or ntpdate
will be no solution for me. But as there is no package for this in
debian I would like to use the ntp stuff instead first.
On Debian systems I'm very happy with the OpenBSD NTP
Pascal Volk wrote:
On Debian systems I'm very happy with the OpenBSD NTP daemon.
Package: openntpd
This ntpd adjusts the local time in little steps.
Also on startup? ntpd uses little steps while running, too. But only at
startup it seems to do a big step.
But as I have found in the
Pascal Volk wrote:
On Debian systems I'm very happy with the OpenBSD NTP daemon.
Package: openntpd
This ntpd adjusts the local time in little steps.
The last I checked openntpd was an SNTP implementation, not NTP.
If it works for you, great.
H
On Sat, Jun 06, 2009 at 08:19:14PM +0200, Arno Wald wrote:
Hallo,
I am running dovecot on a PC (a workstation) to have a mail client
independent storage for my mails. Now I would like to have the system
clock set correctly by using ntpd or ntpdate (using debian/sid).
The problem is,
Juergen wrote:
How will chrony help here if the PC is not online at boot time?
From http://chrony.sunsite.dk/guide/chrony.html
- chronyd can perform usefully in an environment where access to the time
reference is intermittent. chronyd estimates both the current time
offset and the
On Sat, Jun 06, 2009 at 05:06:50PM -0400, Harlan Stenn wrote:
Juergen wrote:
How will chrony help here if the PC is not online at boot time?
From http://chrony.sunsite.dk/guide/chrony.html
- chronyd can perform usefully in an environment where access to the time
reference is
Juergen Daubert wrote:
Chrony is what you are looking for, see http://chrony.sunsite.dk/
chrony does exactly look like what I need. But there is one big
disadvantage when using it on manual dial up PCs: You have to configure
the NTP-servers by IP-address instead of there names. I do not like
Juergen wrote:
Harlan wrote:
There is no corrected version of the real-time clock before the PC goes
online.
I'd suggest to read chrony's manual. Chrony stores the reference values
collected while running online for further use after reboot, even if we
have no online connection at that
Arno Wald wrote:
It would be much better if chrony would look up the server addresses
again when it does recieve the online state command. It seems that
there is no option to turn on such a functionality.
For completeness, even if it is getting OT in this mailing list (Sorry):
39 matches
Mail list logo
