https://bugzilla.novell.com/show_bug.cgi?id=753932
https://bugzilla.novell.com/show_bug.cgi?id=753932#c42
--- Comment #42 from Dr. Werner Fink
Well then the question becomes, shouldn't ntpd be running and why isn't it.
To use ntpd it has to be configured, that is a time server has to added to /etc/ntp.conf which may require a password and a 24/7 network connection. Also the ntpd could be used to access a local DCF clock which has also configured.
What I am asking really is, in a properly installed desktop system, should changes to the system time done via KDE's clock settings (or using date, or using ntpdate) be lost after reboot?
AFAIK the SysVint boot script /etc/init.d/boot.clock has been disabled by Ludwig due to the feature request fate #312407 ... IMHO the wrong decision. Next is that this boot script will not work with systemd as systemd simply mask the clock service. I've no idea if systemd provides a configurable systohc option at shutdown/reboot. Next problenm is that systemd does the clock handling at its own in the binary /lib/systemd/systemd and in /lib/systemd/systemd-timedated. -- 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.