This service will be undergoing maintenance at 00:00 UTC, 2016-09-28. It is expected to last about 1 hours
Bug 3610 - System time incorrect.
System time incorrect.
Status: CLOSED NOTABUG
Product: Red Hat Linux
Classification: Retired
Component: basesystem (Show other bugs)
5.2
All Linux
medium Severity low
: ---
: ---
Assigned To: David Lawrence
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 1999-06-21 03:14 EDT by nicklawson
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 1999-07-01 14:48:28 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description nicklawson 1999-06-21 03:14:38 EDT
Windows likes to have the hardware clock set to local time.
So I set the linux clock config to ARC=true.
But then the sysinit script ends up issuing:

    hwclock -hctosys -A

-A is not a valid option (-a is),
and anyway the version of hwclock on my system
will only accept one option per call.
Comment 1 Bill Nottingham 1999-06-21 12:55:59 EDT
what kind of system do you have?  IIRC, you don't
have 'hwclock' on an alpha, and that's the only platform
where 'ARC' is a meaningful option...
Comment 2 nicklawson 1999-06-22 05:46:59 EDT
Ah, I see.
My /etc/sysconfig/clock said "UTC=true,ARC=false" so I
assumed that ARC was some sort of alternative to UTC.
Now I see that the answer is to have BOTH false.

Despite the plethora of sys.admin. tools, it's difficult
to find out what they do in terms of files. Is this documented
anywhere? sag and nag (spectacularly unhelpful names) where not
initially installed with my system, and only later
did I realise they were actually packages.

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