🚀 go-pugleaf

In <891209141.26202.0.nnrp-04.9e98719c@news.demon.co.uk>, nul@jken.demon.co.uk writes:
>I have my TZ variable set as follows...
>
>SET TZ=GMT0BST,M3.5.0/01:00,M10.5.0/02:00
>as recommended in d.a.
>
>My system clock shows local time, ie corrected 1 hour over the
>weekend.
>
>but in an auto response to a post in demon.test today I get
>
>----------------------------------------------------------
>According to your article's header, it was posted on:
>	29 Mar 1998 22:21:26 GMT
>(Your server's clock is probably wrong.)
>----------------------------------------------------------
>
>I posted the article at 22:21 local time so on the face of it my clock
>*is* wrong because I posted it at 22:21:26 BST, not GMT. 
>
>Can anyone clarify whats happening here? Do I need to do something
>else for DST, or is everything ok and I've just misunderstood the
>message from the auto responder?

I'ld guess it depends on what programs you are using, as different progs
demand different formats for TZ. The basic format is GMT0BST (as per
OS/2 Command Ref) which assumes that summertime starts the first Sunday
in April (i.e. when it starts in the US).

I use NS/2 with Changi, and this demands TZ in the format:

SET TZ=gmt0bst,3,-1,0,3600,10,-1,0,3600,3600

being start and finish month, week, day of week, second of day plus the no of
seconds change (i.e. 1 hr). The prog then looks at local time, sees which time
zone and subtracts one hour to give GMT. E.g. this msg is posted at 19.39 BST
so the news msg will read 18.39 GMT.

Demon's server is simply pointing out to you that the time you claimed to have
posted hasn't yet arrived!

The fact that different progs seem to demand different settings of TZ 
doesn't give me too much confidence in their ability to cope with the millenium
change!
                 
Peter Robins

PS What's d.a.?