--- Kastus wrote:

On Thu, Dec 09, 2004 at 05:40:45PM -0800, Dimych wrote:

...

...

Dimych wrote: Actually, the system halt script (/etc/init.d/halt) updates the hardware clock from the system clock, every time the system shuts down (which includes rebooting, since it uses the same

--- Darryl Gregorash wrote: script). Nope - at least not in SuSE...

Yes, /etc/init.d/halt calls /etc/init.d/boot.d/K11boot.clock which does "/sbin/hwclock --systohc $HWCLOCK"

Probably I should be more specific in my previos post "Nope - at least not in SuSE 9.1 Pro"... /etc/init.d/boot.clock indeed calls hwclock, but /etc/init.d/halt neither calls it nor hwclock on SuSE 9.1 Pro... Dmitry

--- Paul Hewlett wrote:

On my 9.1 pro the halt script calls all scripts in /etc/boot.d/K* amongst which is K11boot.clock. This in turn calls the hwclock command (provided that it is not a 's390' ).

Paul --

That's weird... The only place on my system which call hwclock is /etc/init.d/boot.clock (by the way I do not even have /etc/boot.d). And I can definitely tell that hwclock does not get called during a reboot on my system because it looses clock settings if I do not call hwclock manually. Now I'm wondering how did we end up running the same OS with different set (or versions) of init scripts? I did not modify them... Different ways to install/upgrade the system? Different set of patches? Any ideas? Dmitry

--- "Joe Morris (NTM)" wrote:

Dimych wrote:

...

The only place on my system which call hwclock is /etc/init.d/boot.clock (by the way I do not even have /etc/boot.d). It is /etc/init.d/boot.d

I do have it :)

Don't you have something similar to the following in /etc/init.d/halt: <snip>

Yes I do have something like this in the halt script. The problem is that nothing except /etc/init.d/boot.clock calls hwclock (I did even find/grep in /etc/init.d to be completely sure :) ) Dmitry

--- "Joe Morris (NTM)" wrote:

It is in that section that /etc/init.d/halt references the kill symlinks in /etc/init.d/boot.d, which in turn calls boot.clock, so you are partially correct in that boot.clock is the only script that calls hwclock, but since halt calls boot.clock, it results in also setting your hwclock to system clock on a shutdown or reboot.

Joe Morris

Thanks for the explanation. But the problem is it does not save the date/time if I reboot... The only way to make it preserve time I figured out is to call hwclock manualy every time I change it. That was the main reason I had to learn about NTP :) Dmitry

Kastus, On Thursday 09 December 2004 20:52, Kastus wrote:

On Thu, Dec 09, 2004 at 05:40:45PM -0800, Dimych wrote:

...

--- Darryl Gregorash wrote:

...

Dimych wrote: Actually, the system halt script

(/etc/init.d/halt)

...

updates the hardware clock from the system clock, every time the system shuts down (which includes rebooting, since it uses the same script).

Nope - at least not in SuSE...

Yes, /etc/init.d/halt calls /etc/init.d/boot.d/K11boot.clock which does "/sbin/hwclock --systohc $HWCLOCK"

Nope, at least not in SuSE 9.1 Pro.

Regards, -Kastus

Randall Schulz

Kastus, On Friday 10 December 2004 09:53, Kastus wrote:

On Thu, Dec 09, 2004 at 10:07:20PM -0800, Randall R Schulz wrote:

...

...

Yes, /etc/init.d/halt calls /etc/init.d/boot.d/K11boot.clock which does "/sbin/hwclock --systohc $HWCLOCK"

Nope, at least not in SuSE 9.1 Pro.

Randal, I don't have any live 9.1 installation handy (upgraded all my home systems to 9.2), but I looked at the /etc/init.d/halt in aaa_base-9.1-0.29.i586.rpm and it does have the following stanza:

Two L's -- Randall.

if test -d /etc/init.d/boot.d/ ; then for i in /etc/init.d/boot.d/K*; do test -f $i || continue if test -x "$i" ; then # Active boot scripts, should have their own messages $i stop else ....

Yes, that's there.

Could it be that /etc/init.d/boot.d/K11boot.clock symlink is missing on your system?

Not missing, exactly. I have "/etc/init.d/boot.d/K12boot.clock". K11 is "boot.quota". There are three K09's, one K10, three K13's... etc.

Regards, -Kastus

Randall Schulz