https://bugzilla.novell.com/show_bug.cgi?id=733626 https://bugzilla.novell.com/show_bug.cgi?id=733626#c6 --- Comment #6 from Tony Mechelynck <antoine.mechelynck@belgacom.net> 2012-01-12 21:46:24 CET --- (In reply to comment #5)
The sequence is OK: See /etc/init.d/nscd ### BEGIN INIT INFO # Provides: nscd # Required-Start: $remote_fs $time
If you have not proper internet connection during the boot time it is not a good idea to start ntp as daemon.
Under 11.4 there was no problem; and even now all my networks (lo, eth_s0_0 and a little later dsl0) are "started" (with a green "done" at the right side of the bootup screen) before the ntp service is launched. So why did it work under 11.4 with "true" Sys V init and why doesn't it work now with systemd as a supposedly "fully compatible drop-in replacement"?
Since openSUSE 12.1 you can configure ntp to set the time periodicaly.
How? Shall I add (and in which file in which format?) a cron job to run ntp every so often? And how often? And will that prevent the analog clock on the KDE login screen from showing the wrong time when booting to X11 at "runlevel 5" (or the systemd equivalent)?
Furhteremore, the best way to get the correct time is to keep the CMOS time in UTC. Setting CMOS in local time couses a lot of trouble.
I set it that way under SuSE 6 (6.4 IIRC) because at that time I was running double-boot, and Windows needs the clock on local time. It never gave me any problem until openSUSE 11.4 inclusive. Finally, why can't the shutdown routine (init 0 or init 6) store the current system time in the CMOS so that at next reboot the clock will be set right even if NTP cannot resolve the timeserver hostname to a dotted-quad IP address? (YaST tells me, under "Security and Users → Security Center and Hardening → Security Overview, that "Write back system time to the hardware clock" is "Enabled √") -- 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.