Newsgroups: comp.unix.xenix.misc
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!lavaca.uh.edu!menudo.uh.edu!sugar!ficc!peter
From: peter@ficc.ferranti.com (Peter da Silva)
Subject: Re: The switch to daylight savings time
Message-ID: <SHOAU_1@xds13.ferranti.com>
Keywords: CMOS, date, DST, setclock, time, TZ, Xenix 3.0
Reply-To: peter@ficc.ferranti.com (Peter da Silva)
Organization: Xenix Support, FICC
References: <9@phlpa.UUCP> <PINKAS.91Apr9141415@st860.intel.com> <1991Apr10.114836.10816@convex.com> <5776@vela.acs.oakland.edu>
Date: Fri, 12 Apr 91 20:52:05 GMT

In article <5776@vela.acs.oakland.edu> srodawa@vela.acs.oakland.edu (Ron Srodawa) writes:
> I too have an EST->EDT tale of woe.  I'm running Xenix/386 2.3.3.  Last
> year it did the correct changes all by itself.  This year, I have TCP/IP
> and I'm running timed, the network time daemon.  Xenix advanced the time
> TWO HOURS!  Any ideas about that one?

Xenix doesn't advance the time. It just changes the way time is displayed.

Theory: Your timed is apparently picking up the time from some place that has
the time advanced, converting it to UNIX time without knowing that you
switched to DST, and then setting your clock. Other programs that know it's
DST are then adding the hour as well.

Solution: kill timed and restart it.
-- 
Peter da Silva.  `-_-'  peter@ferranti.com
+1 713 274 5180.  'U`  "Have you hugged your wolf today?"
