Xref: utzoo comp.unix.xenix.misc:155 comp.unix.xenix.sco:2184 Newsgroups: comp.unix.xenix.misc,comp.unix.xenix.sco 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: SCO response to the problem of daylight savings time Message-ID: Keywords: Cron Reply-To: peter@ficc.ferranti.com (Peter da Silva) Organization: Xenix Support, FICC References: <15@phlpa.UUCP> Date: Thu, 11 Apr 91 16:05:36 GMT In article <15@phlpa.UUCP> scott@phlpa.UUCP (Scott Scheingold) writes: > The problem is with the source code to cron. He told me that > when cron is started it then resets itself and counts how many > seconds that it will be until the next time it will run again. > It does not read the clock except for the first time that you > bring up the system. Unless SCO is running a totally bogus implementation of UNIX, this is exactly incorrect. The system time should not change when DST comes in or out... it stays GMT (or UT0, if you prefer). Instead, the interpretation of the time zone is changed either by the kernel's dst flag, tables compiled into "ctime" and "localtime", or by changing the TZ environment variable if the above two techniques fail. I surely hope SCO doesn't actually plan on changing to "Greenwich Daylight Time". I suspect that the SCO tech guy was confused or having problems communicating. Just shut down cron and restart it. No problemo. -- Peter da Silva. `-_-' peter@ferranti.com +1 713 274 5180. 'U` "Have you hugged your wolf today?"