Path: utzoo!attcan!lsuc!eci386!woods
From: woods@eci386.uucp (Greg A. Woods)
Newsgroups: comp.unix.sysv386
Subject: Re: Sysv/386 and Daylight savings time
Summary: it doesn't have to be this complicated
Message-ID: <1990Nov14.043355.4495@eci386.uucp>
Date: 14 Nov 90 04:33:55 GMT
References: <16354@s.ms.uky.edu> <1990Nov13.005923.24658@ico.isc.com>
Reply-To: woods@eci386.UUCP (Greg A. Woods)
Organization: Elegant Communications Inc.
Lines: 30

In article <1990Nov13.005923.24658@ico.isc.com> rcd@ico.isc.com (Dick Dunn) writes:
> kherron@ms.uky.edu (Kenneth Herron) writes:
> > My machine (a 386-clone running AT&T sysv/386 3.2.1) handled the
> > time change properly, but after a system reboot it was off by an
> > hour.  Probably this was due to blindly following the battery-backed
> > clock.
>[....]
> Nothing wrong with the configuration.

Well, I'd claim that the "vendor" forgot to put a line in crontab:

	3 * * * *	setclock

At least one system I use does have this feature.  Of course this
method assumes the system clock is more correct, which is true if one
has a network timed, or if one calls WWV regularly.

> I've often wished there were an option to keep the CMOS clock on GMT.
> Yeah, I know...that would make times look funny in DOS...but I don't use
> DOS, so I don't care.  Seems a pity that the problem arises even tho UNIX
> is perfectly capable of dealing with the DST silliness.

Yup, and that would be easier if the vendors of "PC" (i.e. iX86) UNIX
would support a config option to let the system know you have a GMT
hardware clock, not a wall-time one.
-- 
						Greg A. Woods

woods@{eci386,gate,robohack,ontmoh,tmsoft}.UUCP		ECI and UniForum Canada
+1-416-443-1734 [h]  +1-416-595-5425 [w]    VE3TCP	Toronto, Ontario CANADA