Article View: comp.os.linux.development.system
Article #17Re: A whacky DATE bug in Linux - Problem gets crazier!
From: Dave Blake
Date: Mon, 05 Oct 1998 00:00
Date: Mon, 05 Oct 1998 00:00
46 lines
2880 bytes
2880 bytes
Paul Taylor wrote: >Wolfgang Bornath wrote: >> [snip] >> What do I have here? I have my BIOS on local time (which is Central European >> Summer Time). During installation of Linux (SuSE 5.3, 2.0.35) I told the system >> that I am in TZ Berlin/Europe and that my BIOS is showing local time. >> Now with [date] I get the local time. >> With [date -u] I get UTC time which is 2 hours behind. >> With [hwclock --show] I get local time. >> With [hwclock --utc --show] I get UTC time which is... WHAT NOW? >> As you can see above UTC is with date 2 hours behind and with hwclock 2 hours >> ahead. >"hwclock --utc" is incorrect. My timezone is UTC+10; "date", "date -u" and >"hwclock" show the expected times, but "hwclock --utc" shows the time as >10 hours ahead of local instead of 10 hours behind. Presumably the program >was written by someone in the USA who thought that UTC is always ahead of >local time. RTFM. From the man page on date --------------- -u, --universal Print or set the time and date in Coordinated Universal Time (also known as Greenwich Mean Time) instead of in local (wall clock) time. ------------ From the man page on hwclock ------------- --utc Indicates that the Hardware Clock is kept in Universal Coordinated Time. It is your choice whether to keep your clock in UTC or local time, but nothing in the clock tells which you've chosen. So this option is how you give that information to hwclock. -------------- --- Dave Blake dblake@phy.ucsf.edu
Technical Details
Message-ID:
<slrn71i3m2.3r6.dblake@dylan.ucsf.edu>Path:
arc1-ca.pugleaf.net!unknown!not-for-mailReferences:
<3601D4F7.247C8BC2@usq.edu.au> <3607ABBA.1952C377@uq.net.au> <36087C67.3313582C@usq.edu.au> <360E42BB.CF1DF123@uq.net.au> <907566662.768516518@news.frankfurt.netsurf.de> <36187FCD.774B379C@ozemail.com.au>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: f5392,12de531511895886 X-Google-Attributes: gidf5392,public X-Google-Thread: 10c696,12de531511895886 X-Google-Attributes: gid10c696,public X-Google-Thread: f9382,12de531511895886 X-Google-Attributes: gidf9382,public X-Google-Thread: f9b51,12de531511895886 X-Google-Attributes: gidf9b51,public X-Google-Thread: 100c5f,12de531511895886 X-Google-Attributes: gid100c5f,public X-Google-Thread: ff9be,12de531511895886 X-Google-Attributes: gidff9be,public X-Google-Thread: faa64,12de531511895886 X-Google-Attributes: gidfaa64,public X-Google-Thread: 102983,12de531511895886 X-Google-Attributes: gid102983,public From: dblake@dylan.ucsf.edu (Dave Blake ) Subject: Re: A whacky DATE bug in Linux - Problem gets crazier! Date: 1998/10/05 Message-ID: <slrn71i3m2.3r6.dblake@dylan.ucsf.edu> X-Deja-AN: 397989529 References: <3601D4F7.247C8BC2@usq.edu.au> <3607ABBA.1952C377@uq.net.au> <36087C67.3313582C@usq.edu.au> <360E42BB.CF1DF123@uq.net.au> <907566662.768516518@news.frankfurt.netsurf.de> <36187FCD.774B379C@ozemail.com.au> Organization: UCSF, ITS Reply-To: dblake@phy.ucsf.edu Newsgroups: comp.os.linux.development.system,comp.os.linux.development.apps,comp.os.linux.setup,alt.linux,alt.os.linux,comp.os.linux,comp.os.linux.questions,aus.computers.linux