Xref: utzoo comp.unix.questions:30313 comp.unix.misc:1293
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!cs.utexas.edu!asuvax!ncar!gatech!bloom-beacon!eru!hagbard!sunic!mcsun!ukc!axion!vision!ukpoit!alan
From: alan@ukpoit.co.uk (Alan Barclay)
Newsgroups: comp.unix.questions,comp.unix.misc,comp.unix.386
Subject: Re: The swich with dailight savings time
Keywords: Cron
Message-ID: <1991Apr11.090347.4946@ukpoit.co.uk>
Date: 11 Apr 91 09:03:47 GMT
References: <9@phlpa.UUCP> <1991Apr09.162130.1479@chinet.chi.il.us>
Organization: iT - The Information Technology Business Of The Post Office
Lines: 31

In article <1991Apr09.162130.1479@chinet.chi.il.us> les@chinet.chi.il.us (Leslie Mikesell) writes:
>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.
>>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.

From the man page on my system (NCR tower running V.2),

/* Start of retyped quote  */
RESTRICTIONS

With the introduction of the new database timezone utilities,
the user can tailor the date/hour on which daylight savings
time occcurs. Whenever a change is made, cron must be
restarted, and jobs performed on the first day of the chage
are run one hour later than expected. Job performed on subsequent
days are then run as expected.
/* End of retyped quote */


Therefore somebody knew about it. We get round it by killing cron, just
like TFM says.
-- 
  Alan Barclay
  iT                                |        E-mail : alan@ukpoit.uucp
  Barker Lane                       |        BANG-STYLE : .....!ukc!ukpoit!alan
  CHESTERFIELD S40 1DY              |        VOICE : +44 246 214241