On Fri, 29 Oct 2004 11:45:37 +0200, Istvan Nemeth <[EMAIL PROTECTED]> wrote:
I hope you already sorted this out - my reply is a bit late now. > I don't know how to set back the local time automatically. Things will work automatically. The /etc/localtime file defines the time zone, the offset to UTC for each of the time zones, and then moment where you cut over. The /etc/localtime is normally a copy of the correct timezone from /usr/share/zoneinfo. > I don't want to set the time manually (or with network tools): Linux can > keep the right time, and so LPAR-s times are the same. You hardware clock runs UTC, and does not get changed with DST. Linux obtains the TOD clock with the STCK instruction and computes local time from that UTC timestamp using the /etc/localtime definition. It will automatically do the cut-over. I had a loop run 'date' each second and look what happens: Sun Oct 31 02:59:57 CEST 2004 Sun Oct 31 02:59:58 CEST 2004 Sun Oct 31 02:59:59 CEST 2004 Sun Oct 31 02:00:00 CET 2004 Sun Oct 31 02:00:01 CET 2004 Sun Oct 31 02:00:02 CET 2004 My loop was also creating a small file each second, and even that works: linux10:~ # ls -l --time-style=full-iso file* -rw-r--r-- 1 root root 30 2004-10-31 02:59:57.000000000 +0200 file60.tmp -rw-r--r-- 1 root root 30 2004-10-31 02:59:58.000000000 +0200 file61.tmp -rw-r--r-- 1 root root 30 2004-10-31 02:59:59.000000000 +0200 file62.tmp -rw-r--r-- 1 root root 29 2004-10-31 02:00:00.000000000 +0100 file63.tmp -rw-r--r-- 1 root root 29 2004-10-31 02:00:01.000000000 +0100 file64.tmp So it looks like the filesystem is nicely keeping track of the timestamp and the time zone when the file was created. -- Rob van der Heij rvdheij @ gmail.com ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
