Carlos E. R. wrote:

Aparently, both serve the same purpose:

No, in fact they are exact opposite:

/etc/init.d/boot.clock:

# Description: Read hardware clock and set system clock ^^^^^^^^ ^^^^^^

/etc/init.d/boot.getclock:

# Description: Read system clock and set hardware clock ^^^^^^ ^^^^^^^^

-- Best Regards / S pozdravom, Pavol RUSNAK SUSE LINUX, s.r.o Package Maintainer Lihovarska 1060/12 PGP 0xA6917144 19000 Praha 9, CR prusnak[at]suse.cz http://www.suse.cz --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

On Wed, Jun 18, 2008 at 01:23:01PM +0200, Carlos E. R. wrote:

The Wednesday 2008-06-18 at 13:01 +0200, Pavol Rusnak wrote:

...

Carlos E. R. wrote:

...

Aparently, both serve the same purpose:

No, in fact they are exact opposite:

Yeah, humm, well... small details :-p

...

...

/etc/init.d/boot.clock:

# Description: Read hardware clock and set system clock ^^^^^^^^ ^^^^^^

...

/etc/init.d/boot.getclock:

# Description: Read system clock and set hardware clock

Basically, between both they take care of the clock. Why two scripts, wasn't it possible to make do with one script? Just curious.

Simply because the boot.clock is required to be executed *before* boot.localfs to have the correct time stamp around during mount. On the other hand is using an adjust file requires to write the system clock back *before* unmounting the local file system done by boot.localfs at shutdown. In other words, the insserv program is currently not able to create start and stop links in an asymetric manner. This is what I'm currently implement for insserv(8) to enable insserv(8) to use not only Required-Start, Should-Start, and X-Start-Before but also Required-Stop, Should-Stop, and -Stop-After. Compare with the manual page insserv(8). Werner -- Dr. Werner Fink SuSE LINUX Products GmbH, Maxfeldstrasse 5, Nuernberg, Germany GF: Markus Rex, HRB 16746 (AG Nuernberg) phone: +49-911-740-53-0, fax: +49-911-3206727, www.opensuse.org ------------------------------------------------------------------ "Having a smoking section in a restaurant is like having a peeing section in a swimming pool." -- Edward Burr --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

Stephan Kulow schrieb:

Am Mittwoch, 18. Juni 2008 schrieb Michael Steinhauser:

...

I updated to 11.0 final on a x86_64 laptop an a desktop-pc. On both i have stored local time. Now my system-time shows always two hours later. When i set the time and reboot, it is again set to the wrong time. I can only fix it, when i sync the time with ntp on startup. Because i have on both machines windows, i can't set the time to utc. Is this known asnd how ca it be fixed? I had this problem since 11.0 Beta.

Well, updates from beta to final are not supported :)

You need to fix up the boot.*clock* mess a beta created. Make sure you have boot.getclock and boot.clock insserved.

Greetings, Stephan

Hi, i didn't update directly from Beta, first i updated to RC`s. boot.getclock and boot.clock are on my systems inserted in /etc/init.d. ==================================================== boot.getclock #! /bin/sh # # Copyright (c) 2001-2002 SuSE Linux AG, Nuernberg, Germany. # Copyright (c) 2008 SuSE LINUX Products GmbH, Nuernberg, Germany. # All rights reserved. # # /etc/init.d/boot.getclock # ### BEGIN INIT INFO # Provides: boot.getclock # Required-Start: boot.localfs # Should-Start: # Default-Start: B S # Default-Stop: # Description: Read system clock and set hardware clock # Short-Description: Read system clock and set hardware clock ### END INIT INFO . /etc/rc.status . /etc/sysconfig/clock # # Don't run into trouble due daylight-saving time # USE_ADJFILE=no case "$HWCLOCK" in *-u*) USE_ADJFILE=yes esac test "$USE_ADJFILE" = no && HWCLOCK="$HWCLOCK --noadjfile" rc_reset case "$1" in start|restart) ;; stop) if test "$HOSTTYPE" != "s390" -a "$HOSTTYPE" != "s390x" ; then if test "$SYSTOHC" = "yes" ; then echo -n "Set Hardware Clock to the current System Time" # # Write back to hardware clock and for UTC calculate adjtime # /sbin/hwclock --systohc $HWCLOCK rc_status -v -r fi fi ;; status) rc_failed 4 rc_status -v ;; *) echo "Usage: $0 {start|stop|status|restart}" exit 1 ;; esac rc_exit ================================================ boot.clock #! /bin/sh # # Copyright (c) 2001-2002 SuSE Linux AG, Nuernberg, Germany. # Copyright (c) 2008 SuSE LINUX Products GmbH, Nuernberg, Germany. # All rights reserved. # # /etc/init.d/boot.clock # ### BEGIN INIT INFO # Provides: boot.clock # Required-Start: boot.rootfsck # Should-Start: # X-Start-Before: boot.localfs # Default-Start: B S # Default-Stop: # Description: Read hardware clock and set system clock # Short-Description: Read hardware clock and set system clock ### END INIT INFO . /etc/rc.status . /etc/sysconfig/clock # # Don't run into trouble due daylight-saving time # USE_ADJFILE=no case "$HWCLOCK" in *-u*) USE_ADJFILE=yes esac test "$USE_ADJFILE" = no && HWCLOCK="$HWCLOCK --noadjfile" rc_reset case "$1" in start|restart) # # mkinitrd will set this variable if the system time was older than # the mkinitrd.rpm build time. if test "$SYSTEM_TIME_INCORRECT" != "" ; then echo -n "The system time was incorrect: '$SYSTEM_TIME_INCORRECT'" rc_status -s rc_exit fi # Set and adjust the hardware clock # if test "$HOSTTYPE" = "s390" -o "$HOSTTYPE" = "s390x" ; then echo -n Setting up the system clock # On s390 the hwclock is set outside Linux currently. The kernel # always assumes it to be set to UTC. So if it is set to local # time, we have to compensate for that. We might achieve this # using this special settimeofday(2) linux feature: # Under Linux there is some peculiar `warp clock' semantics # associated to the settimeofday system call if on the very # first call (after booting) that has a non-NULL tz argu- # ment, the tv argument is NULL and the tz_minuteswest field # is nonzero. In such a case it is assumed that the CMOS # clock is on local time, and that it has to be incremented # by this amount to get UTC system time. No doubt it is a # bad idea to use this feature. (settimeofday(2) man page) # But unless someone complains we simply will use date(1) to shift # the system time by the difference between UTC and local time, if # the system clock is set to local time. This will introduce a # minimal shift due to the delay between gettimeofday and # settimeofday, and it only works as long as $0 is executed # exactly once, at boot. case "$HWCLOCK" in *-l*) date $(date -u +'%m%d%H%M%Y.%S') rc_status esac # # Let zic set timezone - if present. # if test -n "$TIMEZONE" -a -x /usr/sbin/zic ; then echo -n Setting up timezone data /usr/sbin/zic -l $TIMEZONE rc_status fi rc_status -v -r else echo -n Setting up the hardware clock # # Read out to hardware clock and for UTC calculate adjtime # write back the system time later at reboot/shutdown time. # if test "$SYSTOHC" = yes -a "$USE_ADJFILE" = yes ; then # # For UTC calculate adjtime # if test ! -s /etc/adjtime ; then echo "0.0 0 0.0" > /etc/adjtime echo "0" >> /etc/adjtime echo "UTC" >> /etc/adjtime fi /sbin/hwclock --adjust $HWCLOCK rc_status fi /sbin/hwclock --hctosys $HWCLOCK rc_status -v -r fi ;; stop) ;; status) rc_failed 4 rc_status -v ;; *) echo "Usage: $0 {start|stop|status|restart}" exit 1 ;; esac rc_exit --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

Dave Plater schrieb:

Michael Steinhauser wrote:

...

I updated to 11.0 final on a x86_64 laptop an a desktop-pc. On both i have stored local time. Now my system-time shows always two hours later. When i set the time and reboot, it is again set to the wrong time. I can only fix it, when i sync the time with ntp on startup. Because i have on both machines windows, i can't set the time to utc. Is this known asnd how ca it be fixed? I had this problem since 11.0 Beta.

You can fix it by enabling the service "boot.clock" in yast2-runlevel. It used to be enabled by default once. It sets the system clock from hardware clock at boot. Regards Dave P --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

Thank you, this fixed it. Both were inaktiv in Yast2 Runlevel. Sorry for my last post, i was to quick in replying --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org