campbell@redsox.bsw.com (Larry Campbell) (04/08/90)
Does anyone know why xclock (X11R3) doesn't grok daylight savings time? My 'date' command says 9:10 but xclock reads 8:10. This certainly seems odd. Particulars: X11R3 from ISC (V1.1) on 386/ix 2.0.2 (SVR3.2). -- Larry Campbell The Boston Software Works, Inc. campbell@redsox.bsw.com 120 Fulton Street wjh12!redsox!campbell Boston, MA 02109
nigel@modcomp.UUCP (Nigel Gamble) (04/09/90)
in article <1561@redsox.bsw.com>, campbell@redsox.bsw.com (Larry Campbell) says: > Does anyone know why xclock (X11R3) doesn't grok daylight savings time? > My 'date' command says 9:10 but xclock reads 8:10. This certainly seems odd. > Particulars: X11R3 from ISC (V1.1) on 386/ix 2.0.2 (SVR3.2). It sounds as if your xclock was linked with an old (certainly pre SVR3.2) version of libc.a. Older versions of the ctime(3) family of functions that convert from system time (the number of seconds since 1st January 1970 GMT) to local time think that daylight savings time starts on the last Sunday in April, which it did until 1986. After that, your xclock should be back in sync with your `date'. Of course, for people using S5R3 outside North America, it is highly likely that their date command is also wrong, since the library still only knows about the American rules for changing to daylight savings time :-( -- Nigel Gamble uunet!modcomp!nigel MODCOMP, an AEG company modcomp!nigel@uunet.UU.NET 1650 W McNab Rd, Ft Lauderdale, FL 33340-6099