https://bugzilla.novell.com/show_bug.cgi?id=774502 https://bugzilla.novell.com/show_bug.cgi?id=774502#c18 Axel Braun <axel.braun@gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |axel.braun@gmx.de --- Comment #18 from Axel Braun <axel.braun@gmx.de> 2013-01-16 17:45:38 UTC --- I was just about to open a new bug on ntp, as I found this one. I actually notice the same issue on a Laptop using WLAN and Networkmanager: After boot and login to KDE, I have to enter the password for kwallet before a network connection is up. ntp uses this time to die without further notice: T520:/home/docb # rcntp status redirecting to systemctl ntp.service - LSB: Network time protocol daemon (ntpd) Loaded: loaded (/etc/init.d/ntp) Active: inactive (dead) since Tue, 15 Jan 2013 15:34:09 +0100; 1 day and 1h ago Process: 1498 ExecStop=/etc/init.d/ntp stop (code=exited, status=0/SUCCESS) Process: 804 ExecStart=/etc/init.d/ntp start (code=exited, status=0/SUCCESS) CGroup: name=systemd:/system/ntp.service Jan 15 15:31:40 T520.axxite.internal ntpd[887]: proto: precision = 0.132 usec Jan 15 15:31:40 T520.axxite.internal ntpd[887]: ntp_io: estimated max descriptors: 1024, initial socket boundary: 16 Jan 15 15:31:40 T520.axxite.internal ntpd[887]: Listen and drop on 0 v4wildcard 0.0.0.0 UDP 123 Jan 15 15:31:40 T520.axxite.internal ntp[804]: Starting network time protocol daemon (NTPD)..done Jan 15 15:31:40 T520.axxite.internal ntpd[887]: Listen and drop on 1 v6wildcard :: UDP 123 Jan 15 15:31:41 T520.axxite.internal ntpd[887]: Listen normally on 2 lo 127.0.0.1 UDP 123 Jan 15 15:31:41 T520.axxite.internal ntpd[887]: Listen normally on 3 lo ::1 UDP 123 Jan 15 15:31:41 T520.axxite.internal ntpd[887]: peers refreshed Jan 15 15:31:41 T520.axxite.internal ntpd[887]: Listening on routing socket on fd #20 for interface updates Jan 15 15:34:09 T520.axxite.internal ntp[1498]: Shutting down network time protocol daemon (NTPD)..done After a restart, ntp works as expected (note that this is one day later!): T520:/home/docb # rcntp restart redirecting to systemctl T520:/home/docb # rcntp status redirecting to systemctl ntp.service - LSB: Network time protocol daemon (ntpd) Loaded: loaded (/etc/init.d/ntp) Active: active (running) since Wed, 16 Jan 2013 18:20:26 +0100; 4s ago Process: 1498 ExecStop=/etc/init.d/ntp stop (code=exited, status=0/SUCCESS) Process: 8118 ExecStart=/etc/init.d/ntp start (code=exited, status=0/SUCCESS) CGroup: name=systemd:/system/ntp.service └ 8150 /usr/sbin/ntpd -p /var/run/ntp/ntpd.pid -g -u ntp:ntp -i /var/lib/ntp -c /etc/ntp.conf Jan 16 18:20:26 T520.axxite.internal ntp[8118]: Starting network time protocol daemon (NTPD)..done Jan 16 18:20:26 T520.axxite.internal ntpd[8150]: ntp_io: estimated max descriptors: 1024, initial socket boundary: 16 Jan 16 18:20:26 T520.axxite.internal ntpd[8150]: Listen and drop on 0 v4wildcard 0.0.0.0 UDP 123 Jan 16 18:20:26 T520.axxite.internal ntpd[8150]: Listen and drop on 1 v6wildcard :: UDP 123 Jan 16 18:20:26 T520.axxite.internal ntpd[8150]: Listen normally on 2 lo 127.0.0.1 UDP 123 Jan 16 18:20:26 T520.axxite.internal ntpd[8150]: Listen normally on 3 wlan0 192.168.1.16 UDP 123 Jan 16 18:20:26 T520.axxite.internal ntpd[8150]: Listen normally on 4 wlan0 fe80::120b:a9ff:feef:6c4c UDP 123 Jan 16 18:20:26 T520.axxite.internal ntpd[8150]: Listen normally on 5 lo ::1 UDP 123 Jan 16 18:20:26 T520.axxite.internal ntpd[8150]: peers refreshed Jan 16 18:20:26 T520.axxite.internal ntpd[8150]: Listening on routing socket on fd #22 for interface updates I dont feel that this is a configuration issue, but correct me if I'm wrong. IMHO ntp should restart after each network connection (i.e. after resume from suspend) -- 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.