[arch-general] Daylight Saving Time canceled in Ukraine, will Arch know?
Beginning this year, Ukraine is switching to year-round DST and will permanently reside in UTC+3 timezone (where it is now). Normally, the switch to UTC+2 would have occurred some time in October, but no longer. How would Arch Linux handle it for the users who do not have NTP configured? Would Arch somehow know not to switch the clock this year or should zoneinfo file for Kiev be updated to reflect this change and to avoid users' clocks being skewed?
On 09/21/2011 12:29 PM, Barton wrote:
Beginning this year, Ukraine is switching to year-round DST and will permanently reside in UTC+3 timezone (where it is now). Normally, the switch to UTC+2 would have occurred some time in October, but no longer.
How would Arch Linux handle it for the users who do not have NTP configured? Would Arch somehow know not to switch the clock this year or should zoneinfo file for Kiev be updated to reflect this change and to avoid users' clocks being skewed?
It looks like there's a fix to the tzdata package in the works to deal with this: https://groups.google.com/group/linux.debian.bugs.dist/browse_thread/thread/... So presumably, once that fix gets released upstream, Arch would pick it up soon after. DR
On Wed, Sep 21, 2011 at 2:52 PM, David Rosenstrauch <darose@darose.net>wrote:
On 09/21/2011 12:29 PM, Barton wrote:
Beginning this year, Ukraine is switching to year-round DST and will permanently reside in UTC+3 timezone (where it is now). Normally, the switch to UTC+2 would have occurred some time in October, but no longer.
How would Arch Linux handle it for the users who do not have NTP configured? Would Arch somehow know not to switch the clock this year or should zoneinfo file for Kiev be updated to reflect this change and to avoid users' clocks being skewed?
It looks like there's a fix to the tzdata package in the works to deal with this:
https://groups.google.com/**group/linux.debian.bugs.dist/** browse_thread/thread/**a44d60ddb9bb6620?pli=1<https://groups.google.com/group/linux.debian.bugs.dist/browse_thread/thread/a44d60ddb9bb6620?pli=1>
So presumably, once that fix gets released upstream, Arch would pick it up soon after.
DR
You can check the current DST dates with "zgrep -v /etc/localtime | grep 2011" Once you get the updated package you can copy the new zoneinfo file from /usr/share/zoneinfo to /etc/localtime. John F.
On Wed, Sep 21, 2011 at 23:27:50 -0400, Jonathan wrote:
You can check the current DST dates with "zgrep -v /etc/localtime | grep 2011" Once you get the updated package you can copy the new zoneinfo file from /usr/share/zoneinfo to /etc/localtime.
You want "zdump -v /etc/localtime | grep 2011" (not zgrep). Also you better symlink your /usr/share/zoneinfo timezone to /etc/localtime (instead of copy), so you'll get future updates automatically. Geert -- geert.hendrickx.be :: geert@hendrickx.be :: PGP: 0xC4BB9E9F This e-mail was composed using 100% recycled spam messages!
On Thu, Sep 22, 2011 at 4:16 AM, Geert Hendrickx <geert@hendrickx.be> wrote:
On Wed, Sep 21, 2011 at 23:27:50 -0400, Jonathan wrote:
You can check the current DST dates with "zgrep -v /etc/localtime | grep 2011" Once you get the updated package you can copy the new zoneinfo file from /usr/share/zoneinfo to /etc/localtime.
You want "zdump -v /etc/localtime | grep 2011" (not zgrep).
Also you better symlink your /usr/share/zoneinfo timezone to /etc/localtime (instead of copy), so you'll get future updates automatically.
Geert
-- geert.hendrickx.be :: geert@hendrickx.be :: PGP: 0xC4BB9E9F This e-mail was composed using 100% recycled spam messages!
Thank you, zdump is what I intended to write. Arch initscripts will replace /etc/localtime on every boot so a symlink will not remain. http://projects.archlinux.org/initscripts.git/tree/rc.sysinit#n224 john_f
On Wed, Sep 21, 2011 at 19:29:17 +0300, Barton wrote:
How would Arch Linux handle it for the users who do not have NTP configured?
Btw, this has nothing to do with NTP (or other time synchrnonisation mechanisms). The system's internal clock uses epoch time, which is timezone independent. The local timezone is only used when *displaying* times in human readable form (eg. date, ls -l, ...). NTP keeps the epoch time correct, but does not care about time zones. Geert -- geert.hendrickx.be :: geert@hendrickx.be :: PGP: 0xC4BB9E9F This e-mail was composed using 100% recycled spam messages!
participants (4)
-
Barton
-
David Rosenstrauch
-
Geert Hendrickx
-
Jonathan