Re: cron missed jobs when clocks went forward
From: Villy Kruse (vek_at_station02.ohout.pharmapartners.nl)
Date: 03/31/04
- Next message: Villy Kruse: "Re: cron missed jobs when clocks went forward"
- Previous message: Dave Hinz: "Re: cron missed jobs when clocks went forward"
- In reply to: Frank Cusack: "Re: cron missed jobs when clocks went forward"
- Next in thread: Mark Daniels: "Re: cron missed jobs when clocks went forward"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: 31 Mar 2004 13:08:02 GMT
On Tue, 30 Mar 2004 16:35:25 -0800,
Frank Cusack <fcusack@fcusack.com> wrote:
>
> Well, I assume your TZ is configured to skip the clock forward at 12.
> Here in the states it happens at 2AM, and not till next week (this year).
> Shouldn't your TZ be BDT now?
>
In most (if not all EU) the time shift forward at 1:00 UTC, that is.
1:00 GMT => 2:00 BST, 2:00 CET => 3:00 CEST, etc. Thus no roling shift
like in the US starting on the Atlantic coast proceeding west until the
Pacific coast 4 hours later. If EU gets more than 3 timezones a roling
shift may become required.
Villy
- Next message: Villy Kruse: "Re: cron missed jobs when clocks went forward"
- Previous message: Dave Hinz: "Re: cron missed jobs when clocks went forward"
- In reply to: Frank Cusack: "Re: cron missed jobs when clocks went forward"
- Next in thread: Mark Daniels: "Re: cron missed jobs when clocks went forward"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|