Re: [Q} AS 2.1 did NOT execute cron job ob 2:30 A.M. SUNDAY ??
From: aaa (mccdba_at_yahoo.com)
Date: 04/05/04
- Next message: Dave: "Login problem"
- Previous message: Benjamin: "High load average"
- In reply to: Andreas Paasch: "Re: [Q} AS 2.1 did NOT execute cron job ob 2:30 A.M. SUNDAY ??"
- Next in thread: Andreas Paasch: "Re: [Q} AS 2.1 did NOT execute cron job ob 2:30 A.M. SUNDAY ??"
- Reply: Andreas Paasch: "Re: [Q} AS 2.1 did NOT execute cron job ob 2:30 A.M. SUNDAY ??"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: 5 Apr 2004 09:59:55 -0700
I understand 2:00 A.M. changed to 3:00 A.M. and skip the 2:30 A.M. cron job.
But SUN and HP work correctly on 2:30 A.M.
In article <pan.2004.04.05.12.58.47.668325@Paasch.Net>, Andreas Paasch says...
>
>Attempting to reach the Kolinahr, aaa wrote:
>
>>Last SUNday (Day light saving time) my cron job on 2:30 A.M. did not execute. I
>>check system the time actually change, but cron job not execute. I have server
>> servers with AS 2.1 e-38 kernel. They all the same.
>>
>> Does anyone know why?
>>
>>
>> Thanks.
>
>Yes.
>If you think closer about it, DST is always initiated at 2 am, jumping one
>hour ahead, so 2.30 _never_ comes around that specific day.
>
>On going back from DST, you will have 2.30 am twice, as DST is ended at
>3am that day, going back to 2am ... so you should run your cronjob at 3.30
>to prevent it from not running at DST start and to prevent it from running
>twice at DST end.
>
>HTH,
>
>/Andreas
>
>--
>#Peace and long life ...
>Registeret Linux user #292411
>
>
- Next message: Dave: "Login problem"
- Previous message: Benjamin: "High load average"
- In reply to: Andreas Paasch: "Re: [Q} AS 2.1 did NOT execute cron job ob 2:30 A.M. SUNDAY ??"
- Next in thread: Andreas Paasch: "Re: [Q} AS 2.1 did NOT execute cron job ob 2:30 A.M. SUNDAY ??"
- Reply: Andreas Paasch: "Re: [Q} AS 2.1 did NOT execute cron job ob 2:30 A.M. SUNDAY ??"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|
