Xref: utzoo comp.unix.questions:30236 comp.unix.misc:1277
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!mips!cs.uoregon.edu!ogicse!intelhf!ichips!iwarp.intel.com!gargoyle!chinet!les
From: les@chinet.chi.il.us (Leslie Mikesell)
Newsgroups: comp.unix.questions,comp.unix.misc,comp.unix.386
Subject: Re: The swich with dailight savings time
Keywords: Cron
Message-ID: <1991Apr09.162130.1479@chinet.chi.il.us>
Date: 9 Apr 91 16:21:30 GMT
References: <9@phlpa.UUCP>
Organization: Chinet - Chicago Public Access UNIX
Lines: 32

In article <9@phlpa.UUCP> scott@phlpa.UUCP (Scott Scheingold) writes:
>I have noticed that some of my cron jobs are running an hour later
>than they are normally run.
> Have I come across a bug with
>SCO UNIX SYS V/386 Rel. 3.2.2. Or is there something that I should
>do to get things back on track (besides a reboot of the system).

It happens on AT&T's 3B2 SysVr3.2 so it it probably a generic sysV
bug.  If you kill and restart cron everything should go back to
normal, at least if the process doing the restarting was logged
in after the switch to DST.

>I was supprised when I found the clock had changed. I am just glad
>that I didn't have anything of real importance that needed to be
>run at a specific time.

The fact that this bug has been allowed to remain and so few people
seemed to notice makes me wonder if anyone is doing anything of
real importance with sysV unix.

>My next question would be when we switch
>back to EST will this become a problem once again.

No, that one is worse - at least on the 3B2's SysVr3.1 it runs everything
in the crontab twice on the day after the switch.  After losing some
important logfiles to this, I've taken to turning off DST before the
switch in the fall, then resetting it manually the next day to make
sure the running cron is killed (so I don't know if it is still a
problem in r3.2).

Les Mikesell
  les@chinet.chi.il.us