Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!zaphod.mps.ohio-state.edu!rpi!bu.edu!polygen!jerry
From: jerry@polygen.uucp (Jerry Sheckel)
Newsgroups: comp.unix.sysv386
Subject: SCO 'date'
Message-ID: <893@stewart.UUCP>
Date: 19 Nov 90 19:34:48 GMT
References: <2@mport.COM> <931@iiasa.UUCP> <1990Nov07.014539.10187@scuzzy.in-berlin.de> <1990Nov8.001536.10818@dell.dell.com> <7@mport.COM> <273C18CA.266B@telly.on.ca>
Reply-To: jerry@stewart.UUCP (Jerry Shekhel)
Organization: Polygen Corporation, Waltham, MA
Lines: 18

Hello.  I'm running SCO Sys V/386 3.2.1 (ODT 1.0).  What the hell is wrong
with the 'date' command?  It actually seems to overwrite the CMOS clock!
I got sick of having to enter the correct time upon bootup, so I deleted
a few lines from /etc/asktimerc, so that all it does is essentially a
"date `setclock`".  This works roughly half the time.  The other half of
the time, the date ends up being a few hours off (not minutes, always hours).
The weird thing is that entering "date `setclock`" from the command line
actually advances the CMOS clock by 5 hours, every time.  Anyone out there
have problems like these?  Any solutions?
--
+-------------------+----------------------+---------------------------------+
| JERRY J. SHEKHEL  | POLYGEN CORPORATION  | When I was young, I had to walk |
| Drummers do it... | Waltham, MA USA      | to school and back every day -- |
|    ... In rhythm! | (617) 890-2175       | 20 miles, uphill both ways.     |
+-------------------+----------------------+---------------------------------+
|           ...! [ princeton mit-eddie bu sunne ] !polygen!jerry             |
|                            jerry@polygen.com                               |
+----------------------------------------------------------------------------+