Bug 3335 - System clock is reset incorrectly on boot
Summary: System clock is reset incorrectly on boot
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: initscripts
Version: 6.0
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: David Lawrence
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 1999-06-08 14:37 UTC by rodsmith
Modified: 2008-05-01 15:37 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 1999-06-23 19:58:44 UTC

Attachments (Terms of Use)

Description rodsmith 1999-06-08 14:37:02 UTC
After upgrading from Red Hat 5.2 to 6.0, I find that Red Hat
sets my hardware clock forward every time I reboot.  The
amount increases with increasing amounts of time shut off
(the clock increments close to an hour after being off
overnight), so I suspect that the init scripts' calls to
/sbin/hwclock are to blame (or, more likely, the default
values in /etc/adjtime -- doing rpm -V initscripts reveals
that this file hasn't been changed on my system since it was

Comment 1 David Lawrence 1999-06-11 22:24:59 UTC
There were some time problems found when using apmd on laptops and
some desktops where the time was set to GMT inappropriately. Please
update to the errata rpm pf apmd at ftp://updates.redhat.com/6.0/i386
and reopen this bug if that doesnt solve your problem.

Comment 2 rodsmith 1999-06-14 00:29:59 UTC
Upgrading the APMD RPM (I'm now using apmd-3.0beta5-8) does *NOT*
solve the problem.  I'm using a FIC PA-2011 motherboard in a desktop
system, and the system clock is set to local time, not GMT.  Time
shifts are not usually in even multiples of an hour.

Comment 3 Bill Nottingham 1999-06-17 21:29:59 UTC
what happens if you comment out the:

$CLOCK --adjust

line in rc.sysinit?

------- Email Received From  "Roderick W. Smith" <rodsmith> 06/17/99 18:11 -------

Comment 4 Bill Nottingham 1999-06-23 19:58:59 UTC
The adjust of the hardware clock is removed as of
initscripts-4.22, available in the next Raw Hide release....

Note You need to log in before you can comment on or make changes to this bug.