Hi Robin.
> Back in October of last year I wrote a daemon to read the time
> from a clock that is locked to the Rugby 60kHz transmissions.
> Since then it has worked perfectly until today when we go into
> BST (DST in the US) where the mktime function fails.
> It seems that mktime is not happy about a positive value for
> isdst in the tm structure - it being zero during the winter!!
> and causing mktime to return 1- (ie. failure).
> Does anyone know if this is a bug in libc5, the way I'm using
> mktime (the code is on my web site) - although its OK according
> to the man page, or if its some peculiarity of today being the
> day it changes from GMT to BST ?
I don't know about the reason for your problem, but I believe it can
be cured by ensuring that the daemon is run with TZ=UTC in the
environment, as that ignores BST completely and puts all time data as
being straight UTC...
> What is the relevance to ham radio (after so many recent
> off-topic posts) - well I'm using the clock to provide a
> reference for the local area IP network (subnet 44.131.161.0).
Personally, I use rdate to synchronise to a known atomic standard, and
base everything on that...
Best wishes from Riley.
+----------------------------------------------------------------------+
| There is something frustrating about the quality and speed of Linux |
| development, ie., the quality is too high and the speed is too high, |
| in other words, I can implement this XXXX feature, but I bet someone |
| else has already done so and is just about to release their patch. |
+----------------------------------------------------------------------+
* ftp://ftp.MemAlpha.cx/pub/rhw/Linux
* http://www.MemAlpha.cx/kernel.versions.html
