[Clfs-support] Clock problem GMT vs. local

[Craig Jackson]

On Tue, Jan 5, 2010 at 9:01 AM, John Bolton <John.Bolton at quest.com> wrote:
> I have configured the system so that the hardware clock uses local time by
> setting UTC=0 in the file /etc/sysconfig/clock. Unfortunately, during boot
> the system halts with a message stating that the file system cannot be
> mounted because the superblock last write time is in the future. It shows
> the last write time as (for example) 10:00 PM and the current time as 2:00
> PM (I’m in PST so there is an 8 hour offset).

I am also in PST and ran into the same issue.

I was able to work around the issue by forcing the setclock script to
start before the mountfs script by renaming
/etc/rc.d/rcsysinit.d/S25setclock to
/etc/rc.d/rcsysinit.d/S15setclock.  I think a newer kernel may be
assuming the hardware clock is set to UTC.  Since this seems to be a
reasonable assumption for a *nix OS, I vote to make this re-ordering
of the boot order permanent, unless someone can find some other side
effects of this.

Craig Jackson
craigmjackson at gmail.com
253-459-5384 cell