Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cornell!uw-beaver!rice!sun-spots-request
From: dlc@vetch.c3.lanl.gov (Dale Carstensen)
Newsgroups: comp.sys.sun
Subject: cron, SunOS 4.0, and Daylight Savings Time
Keywords: Software
Message-ID: <8904141901.AA02983@vetch.c3.lanl.gov>
Date: 3 May 89 12:53:36 GMT
Sender: usenet@rice.edu
Organization: Sun-Spots
Lines: 6
Approved: Sun-Spots@rice.edu
Original-Date: Fri, 14 Apr 89 13:01:51 MDT
X-Sun-Spots-Digest: Volume 7, Issue 264, message 11 of 13

All the cron entries my 4.0 Suns had between (not sure) either 2:00 AM or
2:01 AM and 2:59 AM or 3:00 AM failed to function from April 2, the
"spring forward" night, until the next time I did a "crontab -e."

So there must be a bug in cron, and system administrator's should be aware
that some processes might not be running.