https://bugzilla.novell.com/show_bug.cgi?id=373267 User crrodriguez@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=373267#c1 --- Comment #1 from Cristian Rodriguez 2008-03-24 08:02:36 MST ---

Firstly /etc/init.d/dovecot needs ntp added to its 'Required Start' list.

nope. it needs $time in Should-Start.

Secondly /etc/init.d/ntp needs the named daemon up and running. Although $named is in the /etc/init.d/ntp 'Required Start' list, the ntpdate command gets issued before named is operational, causing ntpdate to fail. A simple work-around is to sleep 3 seconds before issuing the ntpdate command.

That seems to be a different bug. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=373267 User brian@theharrises.plus.com added comment https://bugzilla.novell.com/show_bug.cgi?id=373267#c3 --- Comment #3 from Brian Harris 2008-03-25 10:50:03 MST --- The 6 seconds discrepancy was after 60 hours, which is not abnormal for PC clocks in my experience. I have since discovered the OpenSuse article on SuSE Package Conventions and see that $named should indicate that name resolution is active. There may have been a network glitch causing the ntpdate to fail. I will remove the 3 second delay and monitor the situation over the next week or so and double check that it consistently fails at boot. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=373267 User vdboor-fora@codingdomain.com added comment https://bugzilla.novell.com/show_bug.cgi?id=373267#c5 Diederik van der Boor changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |vdboor-fora@codingdomain.com --- Comment #5 from Diederik van der Boor 2008-05-05 01:19:44 MST --- This bug has a low severity, but I hope this could be bumped up. According to http://wiki.dovecot.org/TimeMovedBackwards running ntpd/ntpdate after dovecot is started could cause dovecot to die immediately. Not something you'd like to see happening when rebooting your server. Note the docs also recommends running ntpd instead of ntpdate from cron. <quote> In some systems ntpd/ntpdate is run at boot, but only after Dovecot has started. That can cause Dovecot to die immediately. If you have this problem, fix your init scripts to run ntpd/ntpdate before Dovecot.</quote> -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.