Bug 3610

Summary: System time incorrect.
Product: [Retired] Red Hat Linux Reporter: nicklawson
Component: basesystemAssignee: David Lawrence <dkl>
Status: CLOSED NOTABUG QA Contact:
Severity: low Docs Contact:
Priority: medium    
Version: 5.2   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 1999-07-01 18:48:28 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description nicklawson 1999-06-21 07:14:38 UTC
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 16:55:59 UTC
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 09:46:59 UTC
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.