why is there two init scripts hwclockfirst.sh and hwclock.sh ?

[Darryl Clarke]

On 28/01/06, lanjelot <lanjelot at mailforce.net> wrote:
> Hello World
>
> I am trying to understand the reason why there is two init scripts for
> the same task: setting the system time from the hardware clock at boot up.
>
> I am not getting why hwclockfirst.sh first runs
> /sbin/hwclock --hctosys
>
> which is going to be over ridden anyway because right after then it runs
> /sbin/hwclock --noadjfile --hctosys
>
> And then hwclock.sh runs this command again
> /sbin/hwclock --hctosys
>
> What is it all about ?

-- this is by no means a technical answer, only the maintainers of the
base/util-linux package can really answer this :P --

On my system both these scripts are not called on startup, but both
_are_ called on shutdown.

It appears to be the result of an older debian bug though.

There are a few more differences between the two files than the one
you stated.  The single variable near the top 'FIRST=no/yes' sets a
few different paths throughout the script for startup/shutdown.

I'm pretty sure It has to do with whether or not hwclock would be able
to read/write necessary system files.

--
~ Darryl  ~ smartssa at gmail.com
http://smartssa.com / http://darrylclarke.com