https://bugzilla.novell.com/show_bug.cgi?id=699400 https://bugzilla.novell.com/show_bug.cgi?id=699400#c12 Robert Davies <rob.opensuse.linux@googlemail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rob.opensuse.linux@googlema | |il.com --- Comment #12 from Robert Davies <rob.opensuse.linux@googlemail.com> 2011-07-10 23:48:08 UTC --- In old versions of NTP, you were expected to STEP the clock first on boot for large discrepancies, and only then slew the time after by cron job, or running NTP daemon. It was no good having many unstable peers & servers. It seems like bar bugs that this need was already accounted for. In /etc/init.d/ntp : start) if [ "$NTPD_FORCE_SYNC_ON_STARTUP" = "yes" ]; then # get the initial date from the timeservers configured in ntp.conf ntpd_is_running || $0 ntptimeset fi And : ntptimeset) NTPD_PROTO="$( get_ntpd_ip_proto )" for i in $(gawk '/^server/ { if( $2 !~ "^127.127." ) print $2","$3 }' $NTP_CONF) do <snip> sntp -t 2 -l /dev/null -s $SNTP_OPT 2> /dev/null && { SYNCHRONISED=$SNTP_OPT; break; }; done if [ "$SYNCHRONISED" ] then echo "Time synchronized with $SYNCHRONISED" else echo "Time could not be synchronized" fi ;; So perhaps simply making the initial & any following daemon starts, where synchronisation has not succeeded with 24 hours, would solve this issue? Adding code, roughly like : if [ "$SYNCHRONISED" ] then echo "Time synchronized with $SYNCHRONISED" touch /var/lib/ntp/ntp-synchronised-start # record synchronisation time else On "ntp start": # test for recent synchronisation test `find /tmp/ntp -name ntp-synchronised-start -mtime -1 -print` || NTPD_FORCE_SYNC_ON_STARTUP=yes if [ "$NTPD_FORCE_SYNC_ON_STARTUP" = "yes" ]; then # get the initial date from the timeservers configured in ntp.conf ntpd_is_running || $0 ntptimeset -- 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.