AS 2.1 did not execute cron job on 2:10 A.M. SUNDAy ???

[Ed Wilts]

On Mon, Apr 05, 2004 at 05:10:12PM +0000, bbaa aaa wrote:
> Thanks.  But I don't think it is bug on SUN, the reason is SUN and HP-UX 
> both work correctly on 2:30 A.M.

So both Solaris and HP-UX are broken.  There is no 2:30 AM, so what time
did the cron jobs actually run?  At 3am (the first increment past 2am),
3:30 am (half-hour after 2am), or 1:30am (half-hour before 3am)? 

They could not have possibly run at 2:30AM when you told them to since
there was no 2:30AM.

        .../Ed
 
> >From: Ed Wilts <ewilts at ewilts.org>
> >To: General Red Hat Linux discussion list <redhat-list at redhat.com>
> >Subject: Re: AS 2.1 did not execute cron job on 2:10 A.M. SUNDAy ???
> >Date: Mon, 5 Apr 2004 09:52:10 -0500
> >
> >On Mon, Apr 05, 2004 at 01:12:05PM +0000, bbaa aaa wrote:
> >> I know day light saving time reset on 2:00 A.M., but SUN server cron job
> >> (2:10 A.M.) work correctly without problem.
> >
> >Then that would be a bug on the SUN servers.  2:10AM didn't exist and I
> >contend that your AS servers did the right thing.
> >
> >        .../Ed
> >
> >> >From: "Tom" <duffer at usa.net>
> >> >To: "General Red Hat Linux discussion list" <redhat-list at redhat.com>
> >> >Subject: RE: AS 2.1 did not execute cron job on 2:10 A.M. SUNDAy ???
> >> >Date: Mon, 5 Apr 2004 08:09:00 -0500
> >> >
> >> >I belive, that the official time to change to daylight savings is 2 A.M 
> >so
> >> >if your system reset the time at 2 A.M, then there was no 2:30 for the 
> >cron
> >> >job to run.  Assuming you went to dailight savings time at 2:00 am.
> >> >
> >> >
> >> >-----Original Message-----
> >> >From: redhat-list-bounces at redhat.com
> >> >[mailto:redhat-list-bounces at redhat.com]On Behalf Of bbaa aaa
> >> >Sent: Monday, April 05, 2004 7:33 AM
> >> >To: redhat-list at redhat.com
> >> >Subject: AS 2.1 did not execute cron job on 2:10 A.M. SUNDAy ???
> >> >
> >> >
> >> >We have Redhat AS 2.1 e-38.  On Sunday all the servers did change time, 
> >but
> >> >cron job on 2:30 A.M. did not execute.
> >> >
> >> >It happen on all servers.
> >> >
> >> >does anyone know why?

-- 
Ed Wilts, Mounds View, MN, USA
mailto:ewilts at ewilts.org
Member #1, Red Hat Community Ambassador Program