From glebius@cell.glebius.int.ru Mon Oct 31 09:27:24 2011 Return-Path: Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D28B1106564A for ; Mon, 31 Oct 2011 09:27:24 +0000 (UTC) (envelope-from glebius@cell.glebius.int.ru) Received: from cell.glebius.int.ru (glebius.int.ru [81.19.64.117]) by mx1.freebsd.org (Postfix) with ESMTP id 5B0D68FC1A for ; Mon, 31 Oct 2011 09:27:24 +0000 (UTC) Received: from cell.glebius.int.ru (localhost [127.0.0.1]) by cell.glebius.int.ru (8.14.4/8.14.4) with ESMTP id p9V9RMeP011516 for ; Mon, 31 Oct 2011 12:27:22 +0300 (MSK) (envelope-from glebius@cell.glebius.int.ru) Received: (from glebius@localhost) by cell.glebius.int.ru (8.14.4/8.14.4/Submit) id p9V9RMnQ011515; Mon, 31 Oct 2011 12:27:22 +0300 (MSK) (envelope-from glebius) Message-Id: <201110310927.p9V9RMnQ011515@cell.glebius.int.ru> Date: Mon, 31 Oct 2011 12:27:22 +0300 (MSK) From: Gleb Smirnoff To: FreeBSD-gnats-submit@freebsd.org Cc: Subject: /etc/localtime is never updated X-Send-Pr-Version: 3.113 X-GNATS-Notify: >Number: 162187 >Category: conf >Synopsis: /etc/localtime is never updated >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs >State: closed >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Mon Oct 31 09:30:15 UTC 2011 >Closed-Date: Mon Oct 31 10:09:03 UTC 2011 >Last-Modified: Mon Oct 31 10:09:03 UTC 2011 >Originator: Gleb Smirnoff >Release: FreeBSD 10.0-CURRENT i386 >Organization: >Environment: System: FreeBSD think 10.0-CURRENT FreeBSD 10.0-CURRENT #12 r226163M: Sun Oct 9 16:17:18 MSD 2011 glebius@think:/usr/obj/usr/src/head/sys/THINKPAD_T60 i386 >Description: By default, the /etc/localtime file isn't a symlink but a copy of timezone selected upon installation with tzsetup. As the system undergoes upgrades, runs installworld, mergemaster, etc, the file /etc/localtime is never touched. For example in my system it is dated year 2004. The problem pops up when the system doesn't change its timezone, but the timezone the system resides in is changed itself. For example new daylight saving policies are published by state. Administator expects that keeping system up to date, or installing a package upon /usr/share/zoneinfo would make his system configured to an updated timezone. >How-To-Repeat: 1) Update your system. 2) ls -l /etc/localtime. >Fix: 1) At job, our network installation process makes /etc/localtime a symlink. All these systems underwent the transition process to new 2011 daylight saving timezone in Russia correctly, unlike the systems installed by sysinstall. We have been running hundreds of installations with symlink for years, and we didn't notice any problems with this approach. 2) If having symlink to /usr/share/zoneinfo in /etc is not feasible for some reason, then some updating tool should check whether the /etc/localtime copy needs to be updated. Probably mergemaster? >Release-Note: >Audit-Trail: State-Changed-From-To: open->closed State-Changed-By: glebius State-Changed-When: Mon Oct 31 10:08:21 UTC 2011 State-Changed-Why: I've found that some of my systems lacked /var/db/zoneinfo, which is required for correct update of /etc/localtime. http://www.freebsd.org/cgi/query-pr.cgi?pr=162187 >Unformatted: