-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I just have seen something in the warn log and I'm investigating. See the detailed log: Feb 12 12:26:54 nimrodel postfix/local[29204]: ED7FE86F23: to=<cer@localhost.nimrodel.valinor>, relay=local, delay=62, status=sent (delivered to command: /usr/bin/procmail) Feb 12 12:26:54 nimrodel postfix/smtpd[29128]: connect from localhost[127.0.0.1] Feb 12 12:26:52 nimrodel postfix/smtpd[29126]: disconnect from localhost[127.0.0.1] Feb 12 12:26:52 nimrodel amavis[26348]: (26348-06-28) FWD via SMTP: <opensuse-es+bounces-6521-robin.listas... Notice the clock jumping back two whole seconds? Well, postfix gives notice: Feb 12 12:26:52 nimrodel postfix/qmgr[4707]: warning: backward time jump detected -- slewing clock ... Feb 12 12:27:34 nimrodel postfix/qmgr[4707]: warning: backward time jump recovered -- back to normality Now, why did the clock jump back two whole seconds? Is postfix adjusting the clock, or is it just noticing it? I'm using ntp, it shouldn't do that! But it does. See the xntpd log: 12 Feb 03:02:53 ntpd[4635]: offset -0.003808 sec freq 10.337 ppm error 0.010344 poll 10 12 Feb 03:03:28 ntpd[4635]: synchronized to 193.127.101.30, stratum 2 (here the system was suspended to disk, thus the lap, from 03:39 to 11:34) 12 Feb 11:35:45 ntpd[4635]: synchronized to 194.146.227.112, stratum 2 12 Feb 11:39:39 ntpd[4635]: synchronized to 193.225.14.163, stratum 2 12 Feb 11:49:13 ntpd[4635]: synchronized to LOCAL(0), stratum 10 12 Feb 11:52:47 ntpd[4635]: synchronized to 194.150.121.14, stratum 2 12 Feb 11:57:24 ntpd[4635]: offset 0.000000 sec freq 10.363 ppm error 0.122509 poll 10 12 Feb 12:26:52 ntpd[4635]: time reset -2.125240 s <====== 12 Feb 12:26:52 ntpd[4635]: system event 'event_clock_reset' (0x05) status 'leap_none, sync_unspec, 15 events, event_peer/strat_chg' (0xf4) 12 Feb 12:26:52 ntpd[4635]: system event 'event_peer/strat_chg' (0x04) status 'leap_none, sync_unspec, 15 events, event_clock_reset' (0xf5) 12 Feb 12:26:54 ntpd[4635]: peer 193.127.101.30 event 'event_reach' (0x84) status 'unreach, conf, 2 events, event_reach' (0x8024) Notice that it is almost one hour after wake up when ntp decides to jump the clock back by two whole seconds, instead of adjusting it slowly. Why? Supposedly, the suspend routines should restart ntp, but it is not happening. I have, in /etc/sysconfig/powersave/sleep: SUSPEND2DISK_RESTART_SERVICES="autofs slmodemd irda ntpd" Obviously, the service has not been restarted, but it was left in memory, thus the error on wake up. Why? How to force it to be stopped and restarted with suspend/wakeup? - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFF0FSytTMYHG2NR9URAo6lAJ0VeeNxZ3UiceCrmK1uNNQbGUT/YgCcCgAx br3nfp3dB2497EeNukj+JPs= =Y6Gl -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org