Clock did not adjust for daylight saving - Suse

This is a discussion on Clock did not adjust for daylight saving - Suse ; ibuprofin@painkiller.example.tld (Moe Trin) writes: >On Tue, 06 Nov 2007, in the Usenet newsgroup alt.os.linux.suse, in article > , Unruh wrote: >>And if the legislatures around the world decide to change things >>again, within a week there will be a new ...

+ Reply to Thread
Page 2 of 2 FirstFirst 1 2
Results 21 to 23 of 23

Thread: Clock did not adjust for daylight saving

  1. Re: Clock did not adjust for daylight saving

    ibuprofin@painkiller.example.tld (Moe Trin) writes:

    >On Tue, 06 Nov 2007, in the Usenet newsgroup alt.os.linux.suse, in article
    >, Unruh wrote:


    >>And if the legislatures around the world decide to change things
    >>again, within a week there will be a new tzdata file which
    >>incorporates those changes and within a month all distros will have
    >>distrubuted it.


    >That's a heck of a lot of confidence in the various distribution
    >maintainers. More that I have in them.


    >-rw-r--r-- 1 8800 0 157506 Jan 8 17:28 tzdata2007a.tar.gz
    >-rw-r--r-- 1 8800 0 157432 Feb 12 14:34 tzdata2007b.tar.gz
    >-rw-r--r-- 1 8800 0 158198 Feb 26 14:09 tzdata2007c.tar.gz
    >-rw-r--r-- 1 8800 0 159373 Mar 20 12:48 tzdata2007d.tar.gz
    >-rw-r--r-- 1 8800 0 159753 Apr 2 14:11 tzdata2007e.tar.gz
    >-rw-r--r-- 1 8800 0 160513 May 7 14:46 tzdata2007f.tar.gz
    >-rw-r--r-- 1 8800 0 161080 Aug 20 14:48 tzdata2007g.tar.gz
    >-rw-r--r-- 1 8800 0 162187 Oct 1 14:05 tzdata2007h.tar.gz
    >-rw-r--r-- 1 8800 0 162977 Nov 1 14:16 tzdata2007i.tar.gz


    >While it is true that some of those source files are making relatively
    >inconsequential changes, they all effect _someone_ out there. 2006g
    >effected Oz and the US, while 2007h changed Egypt, Iran, Palestine,
    >and Brazil. 2007i only changes Syria and Cuba.


    But tzdata2007i includes all of the changes of the previous 11 files. So
    the distro maintainers just have to put in the latest one. They are
    cumulative, as you know. And changes almost always occur with a time lag.
    Ie, a legislative change today, which is probably incorporated in the next
    tzdata file, almost always does not actually change anything for at least a
    year. That is lots of time for the maintainers to get the change out.



    > Old guy


  2. Re: Clock did not adjust for daylight saving

    Unruh wrote:
    >ibuprofin@painkiller.example.tld (Moe Trin) writes:


    >>On Mon, 05 Nov 2007, in the Usenet newsgroup alt.os.linux.suse, in article
    >><_cOdneGoztu5jrLanZ2dnUVZ_oGjnZ2d@insightbb.com>, Pat wrote:


    >>>For some reason the clock on my openSUSE 10.2 system did not adjust for
    >>>daylight savings.


    >>Let's start by asking what timezone you are set for, and how your
    >>system is set (HW clock on localtime? Windoze?) Assuming the USA
    >>and Eastern time zone, what do you see when you do


    >>[pathfinder ~]$ /usr/sbin/zdump -v US/Eastern | grep 2007
    >>US/Eastern Sun Mar 11 06:59:59 2007 GMT = Sun Mar 11 01:59:59 2007 EST isdst=0
    >>US/Eastern Sun Mar 11 07:00:00 2007 GMT = Sun Mar 11 03:00:00 2007 EDT isdst=1
    >>US/Eastern Sun Nov 4 05:59:59 2007 GMT = Sun Nov 4 01:59:59 2007 EDT isdst=1
    >>US/Eastern Sun Nov 4 06:00:00 2007 GMT = Sun Nov 4 01:00:00 2007 EST isdst=0
    >>[pathfinder ~]$ /sbin/hwclock --show ; date ; date -u
    >>Mon Nov 6 00:11:38 2007 -0.101390 seconds
    >>Mon Nov 5 17:11:38 MST 2007
    >>Tue Nov 6 00:11:38 UTC 2007
    >>[pathfinder ~]$


    >>Here, my hardware clock is set to UTC, and my local timezone is 5 hours
    >>behind UTC.


    >>What 'zone files' are you using? From a command line as above, run the
    >>command 'rpm -qa | grep tzdata' and you want to see it reporting a
    >>file later than 'tzdata2005m' (year 2005, m=13th revision). openSUSE 10.2
    >>dates from the end of 2006, so it _should_ have the "current" file unless
    >>you are in Indiana where the politicians were continuing to screw with the
    >>rules as late as tzdata2007g.


    >>>Does the clock not periodically synchronize (like once or twice a day)
    >>>with a time server by default.


    >>Not unless you set it up separately - but that really doesn't matter
    >>because Internet time servers speak only UTC and haven't a clue about
    >>ANY timezone, much less when DST may or may not change things. I'm near
    >>Phoenix, Arizona, and we don't observe DST in this state except in the
    >>Navajo Nation (Northeast part of the state) which does, except within
    >>the Hopi Nation (within the Navaho Nation boundries, within Arizona)
    >>which also ignores DST, except in the town of Jeddito (within the Hopi
    >>Nation boundries, within the Navaho Nation boundries, within Arizona)
    >>which does use DST. No, I'm not making this up.


    >>>If not, is there a way to set this up?


    >>NTP isn't going to solve the DST issue, as it only knows UTC.



    >His problem is that his hardware clock is not properly setting his system
    >time at boot up I suspect. Linux also knows only UTC when it is running.
    >The /etc/localtime file is only used to interpret utc for the user when
    >displaying times to the user. Linux is UTC.


    >So I suspect that his timezone is set up fine. It is his hardware clock
    >that is the problem.


    Either that or he did not download the patches for the new
    daylight savings time rules in the US.

    --
    --- Paul J. Gans

  3. Re: Clock did not adjust for daylight saving

    On Wed, 07 Nov 2007, in the Usenet newsgroup alt.os.linux.suse, in article
    , Unruh wrote:

    >ibuprofin@painkiller.example.tld (Moe Trin) writes:


    >> Unruh wrote:


    >>> And if the legislatures around the world decide to change things
    >>> again, within a week there will be a new tzdata file which
    >>> incorporates those changes


    Don't forget that while the tzdata files are hosted on a government
    server, it's not an official service of the NIH (NIH is part of the
    Department of Health and Human Services, while the somewhat more
    appropriate NIST - the former NBS - is part of the Department of
    Commerce), any more than the writing of Ethernet drivers was a service
    of NASA-Goddard (Donald Becker was a _contractor_ employee there, and
    NASA allowed him space on the FTP server). Additionally, it seems that
    no government entity has the requirement (or even any reason) to keep
    the tzdata file maintainers appraised of pending changes. Look in
    each of the source files, where you will find

    [compton ~]$ head -6 time.2007i/asia
    # @(#)asia 8.13
    #


    # This data is by no means authoritative; if you think you know better,
    # go ahead and edit the file (and please send any changes to
    # tz@elsie.nci.nih.gov for general use in the future).
    [compton ~]$

    >>While it is true that some of those source files are making relatively
    >>inconsequential changes, they all effect _someone_ out there. 2006g
    >>effected Oz and the US, while 2007h changed Egypt, Iran, Palestine,
    >>and Brazil. 2007i only changes Syria and Cuba.

    >
    >But tzdata2007i includes all of the changes of the previous 11 files. So
    >the distro maintainers just have to put in the latest one. They are
    >cumulative, as you know.


    True - but in my experience it _seems_ that distribution changes only
    get in quickly when that change DIRECTLY effects the maintainers.
    Thus, tzdata2007g has been included in a number of distributions, but
    not 2007h or 2007i.

    >And changes almost always occur with a time lag. Ie, a legislative
    >change today, which is probably incorporated in the next tzdata file,
    >almost always does not actually change anything for at least a year.
    >That is lots of time for the maintainers to get the change out.


    I take it you aren't doing 'diff's of the source files.

    [compton ~]$ ls -l time.2007i/DIFFS.200*7.* | cut -c35-
    7411 Jan 9 2007 time.2007i/DIFFS.2006.p-2007.a
    3275 Feb 13 2007 time.2007i/DIFFS.2007.a-b
    6858 Feb 27 2007 time.2007i/DIFFS.2007.b-c
    10437 Mar 20 2007 time.2007i/DIFFS.2007.c-d
    1726 Apr 2 2007 time.2007i/DIFFS.2007.d-e
    3483 May 7 2007 time.2007i/DIFFS.2007.e-f
    14389 Aug 20 16:54 time.2007i/DIFFS.2007.f-g
    6851 Oct 1 16:59 time.2007i/DIFFS.2007.g-h
    2607 Nov 1 16:58 time.2007i/DIFFS.2007.h-i
    [compton ~]$

    Some of the changes are reported retroactively - the changes to the
    'asia' file in the last two are all after-the-fact. The Brazilian
    change in 2007h was reported a week before it took effect. That's
    when the tzdata maintainers published the change - never mind the
    change getting to the various distribution maintainers and actually
    being made available to the users.

    I repeat - you have a heck of a lot of confidence in the various
    distribution maintainers.

    Old guy

+ Reply to Thread
Page 2 of 2 FirstFirst 1 2