[opensuse] Time Incorrect in New Installed opensuse 11.1
I have a new installed opensuse 11.1, and when I boot my opensuse, the time displays the wrong time. and I have to correct it. I really dunnt want to see my days past that fast... I have the same problem in brand new installed opensuse 11.0, and I can find "timezone" update in yast, and I can make it work correctly by update. But I still can not find a solution to the opensuse 11.1, nothing in repos' update. Can anybody help ? Thankyou! -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
vsu wrote:
I have a new installed opensuse 11.1, and when I boot my opensuse, the time displays the wrong time. and I have to correct it. I really dunnt want to see my days past that fast...
I have the same problem in brand new installed opensuse 11.0, and I can find "timezone" update in yast, and I can make it work correctly by update.
But I still can not find a solution to the opensuse 11.1, nothing in repos' update.
Can anybody help ?
Thankyou!
During time configuration are you telling it that hardware clock is set to UTC or localtime? If you are setting to localtime, try setting the hardware clock to UTC and see if that fixes it for you. -Matt -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday, 2009-03-15 at 00:06 +0800, vsu wrote:
I have a new installed opensuse 11.1, and when I boot my opensuse, the time displays the wrong time. and I have to correct it. I really dunnt want to see my days past that fast...
Describe "wrong time". Is it wrong after boot by a fixed amount, and after correction it stays good till next boot? How much is it wrong? Or does it run fast, or slow, and by what amount? Please give details. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkm77DYACgkQtTMYHG2NR9UMkwCbBJpek6dpyxTwQccX0NIJYI5G NJ0AniolwSob8Tufepe1w9BvnH39DSX0 =03Sj -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Carlos E. R. wrote:
On Sunday, 2009-03-15 at 00:06 +0800, vsu wrote:
I have a new installed opensuse 11.1, and when I boot my opensuse, the time displays the wrong time. and I have to correct it. I really dunnt want to see my days past that fast...
Describe "wrong time". Is it wrong after boot by a fixed amount, and after correction it stays good till next boot? How much is it wrong? Or does it run fast, or slow, and by what amount?
Please give details.
Particularly, is it off by the difference between your local time and GMT? If so, you made a configuration error when you chose your hardware clock error. -- Use OpenOffice.org http://www.openoffice.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Carlos E. R. wrote:
On Sunday, 2009-03-15 at 00:06 +0800, vsu wrote:
I have a new installed opensuse 11.1, and when I boot my opensuse, the time displays the wrong time. and I have to correct it. I really dunnt want to see my days past that fast...
Describe "wrong time". Is it wrong after boot by a fixed amount, and after correction it stays good till next boot? How much is it wrong? Or does it run fast, or slow, and by what amount?
Please give details.
Particularly, is it off by the difference between your local time and GMT? If so, you made a configuration error when you chose your hardware clock error.
I did not have internet connecting in my opensuse, so it should not be able to know the GMT. 11.1 would process about 12 hours or less after each time I booted into it. and it would change the BIOS time. I think the post here got the same problem: http://forums.opensuse.org/install-boot-login/409256-time-set-incorrectly-bo... -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
vsu wrote:
Carlos E. R. wrote:
On Sunday, 2009-03-15 at 00:06 +0800, vsu wrote:
I have a new installed opensuse 11.1, and when I boot my opensuse, the time displays the wrong time. and I have to correct it. I really dunnt want to see my days past that fast...
Describe "wrong time". Is it wrong after boot by a fixed amount, and after correction it stays good till next boot? How much is it wrong? Or does it run fast, or slow, and by what amount?
Please give details.
Particularly, is it off by the difference between your local time and GMT? If so, you made a configuration error when you chose your hardware clock error.
I did not have internet connecting in my opensuse, so it should not be able to know the GMT. 11.1 would process about 12 hours or less after each time I booted into it. and it would change the BIOS time. I think the post here got the same problem: http://forums.opensuse.org/install-boot-login/409256-time-set-incorrectly-bo...
When you install Linux, you're given the choice of setting your hardware clock to UTC or local time. Windows requires local time. If you select UTC, but actually use local time, your clock will be off by the difference from UTC. You do not require an internet connection to have this error. If you choose GMT Linux will add an offset to the hardware clock time to display local time. If you chose GMT and the hardware is local time, that offset will cause your clock to be off by the difference between GMT & local time. BTW, GMT used to refer to the "official" clock, but that use has been replaced by UTC. GMT is very slightly off from UTC and it's best to simply consider GMT as a time zone, for the purposes of offset calculation. -- Use OpenOffice.org http://www.openoffice.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
2009/3/14 James Knott
vsu wrote:
Carlos E. R. wrote:
On Sunday, 2009-03-15 at 00:06 +0800, vsu wrote:
I have a new installed opensuse 11.1, and when I boot my opensuse, the time displays the wrong time. and I have to correct it. I really dunnt want to see my days past that fast...
Describe "wrong time". Is it wrong after boot by a fixed amount, and after correction it stays good till next boot? How much is it wrong? Or does it run fast, or slow, and by what amount?
Please give details.
Particularly, is it off by the difference between your local time and GMT? If so, you made a configuration error when you chose your hardware clock error.
I did not have internet connecting in my opensuse, so it should not be able to know the GMT. 11.1 would process about 12 hours or less after each time I booted into it. and it would change the BIOS time. I think the post here got the same problem: http://forums.opensuse.org/install-boot-login/409256-time-set-incorrectly-bo...
When you install Linux, you're given the choice of setting your hardware clock to UTC or local time. Windows requires local time. If you select UTC, but actually use local time, your clock will be off by the difference from UTC. You do not require an internet connection to have this error. If you choose GMT Linux will add an offset to the hardware clock time to display local time. If you chose GMT and the hardware is local time, that offset will cause your clock to be off by the difference between GMT & local time.
Yup, telling Linux to use UTC and dual booting with Windows would cause this, either uncheck the UTC option in "yast timezone" or keep UTC and drop Windows :p
BTW, GMT used to refer to the "official" clock, but that use has been replaced by UTC. GMT is very slightly off from UTC and it's best to simply consider GMT as a time zone, for the purposes of offset calculation.
Regards, -- Ciro Iriarte http://cyruspy.wordpress.com -- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 vsu wrote:
Carlos E. R. wrote:
On Sunday, 2009-03-15 at 00:06 +0800, vsu wrote:
I have a new installed opensuse 11.1, and when I boot my opensuse, the time displays the wrong time. and I have to correct it. I really dunnt want to see my days past that fast...
Describe "wrong time". Is it wrong after boot by a fixed amount, and after correction it stays good till next boot? How much is it wrong? Or does it run fast, or slow, and by what amount?
Please give details.
Particularly, is it off by the difference between your local time and GMT? If so, you made a configuration error when you chose your hardware clock error.
I did not have internet connecting in my opensuse, so it should not be able to know the GMT. 11.1 would process about 12 hours or less after each time I booted into it. and it would change the BIOS time. I think the post here got the same problem: http://forums.opensuse.org/install-boot-login/409256-time-set-incorrectly-bo...
Hi vsu, For reference, please show me your /etc/fstab. If you have a separate partition for /usr, it may cause time problem. Best, - -- _/_/ Satoru Matsumoto - openSUSE Member - Japan _/_/ _/_/ Marketing/Weekly News/openFATE Screening Team _/_/ _/_/ mail: helios_reds_at_gmx.net / irc: HeliosReds _/_/ _/_/ http://blog.geeko.jp/author/heliosreds _/_/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iEYEARECAAYFAkm8a0IACgkQXnHIfHE6+z2BgACfb5u3p8TET7NQGbPQROObIKmC sgoAoJBq6k3hAlWvEQqUGqvKsh8I+GSo =gc7X -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
2009/3/14 Satoru Matsumoto
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
vsu wrote:
Carlos E. R. wrote:
On Sunday, 2009-03-15 at 00:06 +0800, vsu wrote:
I have a new installed opensuse 11.1, and when I boot my opensuse, the time displays the wrong time. and I have to correct it. I really dunnt want to see my days past that fast...
Describe "wrong time". Is it wrong after boot by a fixed amount, and after correction it stays good till next boot? How much is it wrong? Or does it run fast, or slow, and by what amount?
Please give details.
Particularly, is it off by the difference between your local time and GMT? If so, you made a configuration error when you chose your hardware clock error.
I did not have internet connecting in my opensuse, so it should not be able to know the GMT. 11.1 would process about 12 hours or less after each time I booted into it. and it would change the BIOS time. I think the post here got the same problem: http://forums.opensuse.org/install-boot-login/409256-time-set-incorrectly-bo...
Hi vsu,
For reference, please show me your /etc/fstab.
If you have a separate partition for /usr, it may cause time problem.
That one is new
Best,
- -- _/_/ Satoru Matsumoto - openSUSE Member - Japan _/_/ _/_/ Marketing/Weekly News/openFATE Screening Team _/_/ _/_/ mail: helios_reds_at_gmx.net / irc: HeliosReds _/_/ _/_/ http://blog.geeko.jp/author/heliosreds _/_/
Regards, -- Ciro Iriarte http://cyruspy.wordpress.com -- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Carlos E. R. wrote:
On Sunday, 2009-03-15 at 00:06 +0800, vsu wrote:
I have a new installed opensuse 11.1, and when I boot my opensuse, the time displays the wrong time. and I have to correct it. I really dunnt want to see my days past that fast...
Describe "wrong time". Is it wrong after boot by a fixed amount, and after correction it stays good till next boot? How much is it wrong? Or does it run fast, or slow, and by what amount?
Please give details.
Particularly, is it off by the difference between your local time and GMT? If so, you made a configuration error when you chose your hardware clock error.
I did not have internet connecting in my opensuse, so it should not be able to know the GMT. 11.1 would process about 12 hours or less after each time I booted into it. and it would change the BIOS time. I think the post here got the same problem: http://forums.opensuse.org/install-boot-login/409256-time-set-incorrectly-bo...
Hi vsu,
For reference, please show me your /etc/fstab.
If you have a separate partition for /usr, it may cause time problem. Yes, I do have a separate partition for /usr. and this is the fstab:
/dev/disk/by-id/ata-Hitachi_HTS541610J9SA00_SB23B1SHGDGNME-part7 swap swap defaults 0 0 /dev/disk/by-id/ata-Hitachi_HTS541610J9SA00_SB23B1SHGDGNME-part9 / ext3 acl,user_xattr 1 1 /dev/disk/by-id/ata-Hitachi_HTS541610J9SA00_SB23B1SHGDGNME-part8 /boot ext3 acl,user_xattr 1 2 /dev/disk/by-id/ata-Hitachi_HTS541610J9SA00_SB23B1SHGDGNME-part12 /home ext3 acl,user_xattr 1 2 /dev/disk/by-id/ata-Hitachi_HTS541610J9SA00_SB23B1SHGDGNME-part11 /usr ext3 acl,user_xattr 1 2 /dev/disk/by-id/ata-Hitachi_HTS541610J9SA00_SB23B1SHGDGNME-part10 /var ext3 acl,user_xattr 1 2 /dev/disk/by-id/ata-Hitachi_HTS541610J9SA00_SB23B1SHGDGNME-part1 /windows/C ntfs-3g users,gid=users,fmask=133,dmask=022,locale=en_US.UTF-8 0 0 /dev/disk/by-id/ata-Hitachi_HTS541610J9SA00_SB23B1SHGDGNME-part2 /windows/D ntfs-3g users,gid=users,fmask=133,dmask=022,locale=en_US.UTF-8 0 0 /dev/disk/by-id/ata-Hitachi_HTS541610J9SA00_SB23B1SHGDGNME-part6 /windows/F ntfs-3g users,gid=users,fmask=133,dmask=022,locale=en_US.UTF-8 0 0 proc /proc proc defaults 0 0 sysfs /sys sysfs noauto 0 0 debugfs /sys/kernel/debug debugfs noauto 0 0 usbfs /proc/bus/usb usbfs noauto 0 0 devpts /dev/pts devpts mode=0620,gid=5 0 0 /dev/disk/by-id/ata-Hitachi_HTS541610J9SA00_SB23B1SHGDGNME-part5 /windows/E ntfs-3g users,gid=users,fmask=133,dmask=022,locale=en_US.UTF-8 0 0 -------------------------- I dunnt give the choice of setting your hardware clock to UTC. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
vsu wrote:
For reference, please show me your /etc/fstab.
If you have a separate partition for /usr, it may cause time problem.
Yes, I do have a separate partition for /usr. and this is the fstab:
Don't get too excited about this. I'd be very surprised if either of these had anything to do with the clock error. -- Use OpenOffice.org http://www.openoffice.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday, 2009-03-15 at 08:12 -0400, James Knott wrote:
If you have a separate partition for /usr, it may cause time problem. Yes, I do have a separate partition for /usr. and this is the fstab:
Don't get too excited about this. I'd be very surprised if either of these had anything to do with the clock error.
https://bugzilla.novell.com/show_bug.cgi?id=426270 It appears that when the CMOS clock keeps localtime (and he does: /etc/sysconfig/clock:HWCLOCK="--localtime), and there is a separate /usr partition (and he does), the init script can not access the timezone info, and sets the clock incorrectly. At the start of the bugzilla it appears suse people wants the poster to change cmos to utc time - but this will break windows time, but they don't seem to understand or care. #44 description #59 hack ]> put on the stage 3 and 5 of the following: ]> /etc/init.d/boot.clock restart #62 hints that ntp may spoil things #66 found bug, race condition re /dev/rtc ##75 re /usr #76 a hack for 11.1 ] A change that fixes my problems: ] Instead of having a soft link, I copied /usr/share/zoneinfo/America/Phoenix to ] /etc/localtime. Now, on boot and all reboots, the time is continuous and ] correct in /var/log/messages and in the display clock. (!) - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkm9ApcACgkQtTMYHG2NR9VrWQCfYTP/lUTvDM4exrjbkdesMH04 HKoAoI+qIc2Z7V+QSgeT9iWKty59wYvx =ilbf -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
If you have a separate partition for /usr, it may cause time problem. Yes, I do have a separate partition for /usr. and this is the fstab:
Don't get too excited about this. I'd be very surprised if either of these had anything to do with the clock error.
https://bugzilla.novell.com/show_bug.cgi?id=426270
It appears that when the CMOS clock keeps localtime (and he does: /etc/sysconfig/clock:HWCLOCK="--localtime), and there is a separate /usr partition (and he does), the init script can not access the timezone info, and sets the clock incorrectly.
At the start of the bugzilla it appears suse people wants the poster to change cmos to utc time - but this will break windows time, but they don't seem to understand or care.
#44 description
#59 hack ]> put on the stage 3 and 5 of the following: ]> /etc/init.d/boot.clock restart
#62 hints that ntp may spoil things
#66 found bug, race condition re /dev/rtc
##75 re /usr
#76 a hack for 11.1
] A change that fixes my problems: ] Instead of having a soft link, I copied /usr/share/zoneinfo/America/Phoenix to ] /etc/localtime. Now, on boot and all reboots, the time is continuous and ] correct in /var/log/messages and in the display clock. (!)
- -- Cheers, Carlos E. R. Perfect Good ! Thankyou !!! But anybody knows that what does the opensuse 11.0's timezone patch do to the same problem ?
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sunday 15 March 2009 08:28:49 Carlos E. R. wrote:
At the start of the bugzilla it appears suse people wants the poster to change cmos to utc time - but this will break windows time, but they don't seem to understand or care.
Some developers feel it's not their job to work around flaws in software written by other people. -- Boyd Stephen Smith Jr. ,= ,-_-. =. bss@iguanasuicide.net ((_/)o o(\_)) ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-' http://iguanasuicide.net/ \_/
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday, 2009-03-15 at 13:52 -0500, Boyd Stephen Smith Jr. wrote:
On Sunday 15 March 2009 08:28:49 Carlos E. R. wrote:
At the start of the bugzilla it appears suse people wants the poster to change cmos to utc time - but this will break windows time, but they don't seem to understand or care.
Some developers feel it's not their job to work around flaws in software written by other people.
We can not change how Windows works. The fact is that Windows needs and sets the CMOS clock in local time, and AFAIK, there is no way to change that. Users are powerless in this respect. No choice. It is also a fact that Windows does not care about any other operating system. Rather, they care for rising obstacles in our road, to their advantage. Thus it remains the, also a fact of life, that Linux needs to work around the quirks of Windows, if we want to gain users to come from Windows to us, and who will be double booting for at least some time, sharing files, etc. It is also us who need not to raise obstacles of our own in our way. Besides that, SuSE has always known this "quirk" of Windows and worked around it since always. Ie, setting the CMOS to local time, and making /etc/localtime a copy instead of link. It appears that some people on SUSE/Novell do not know/remember this, also, fact. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkm9aKUACgkQtTMYHG2NR9U99gCeI503A9kytZP67lZR0KJsQ2z7 t5YAnixJgb7agsJ6cWwZweQo1NO4KW6z =w84r -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sunday 15 March 2009 15:44:16 Carlos E. R. wrote:
Linux needs to work around the quirks of Windows,
You are welcome to if you want. I'm not going to spend my time working around flaws in proprietary software. I'd actually prefer the developers not either, but that's their choice. I didn't pay for openSUSE (or any of my Linux installations) so they aren't on my dime.[1] POSIX, XPG, and SUS have been around longer than MS Windows and are *the* OS standard. Microsoft should feel free to get with the program. I don't think bending to the will of a convicted monopolist is the way to build an OS, but rather to take existing technical standards[2] and being (0) a fully compliant, (1) the most efficient, (2) the most developer- (3) and user- friendly, and (4) the most featureful implementation available (in that order[3]). Linux does not *need* to work around the quirks of Windows. You want it to, and I can respect that position even if I don't agree with it. -- Boyd Stephen Smith Jr. ,= ,-_-. =. bss@iguanasuicide.net ((_/)o o(\_)) ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-' http://iguanasuicide.net/ \_/ [1] If they were on "my dime", I have a large TODO list that has nothing to do with any MS product. [2] Beyond the 3 I mentioned, there are a host of technical standards published by ISO, IEEE, IETF, W3C, ECMA, etc., etc. that are relevant to openSUSE in particular and modern computer systems in general. [3] I'm willing to negotiate on the order of 1-4, but not the goals themselves.
Satoru Matsumoto wrote:
vsu wrote:
Carlos E. R. wrote:
On Sunday, 2009-03-15 at 00:06 +0800, vsu wrote:
I have a new installed opensuse 11.1, and when I boot my opensuse, the time displays the wrong time. and I have to correct it. I really dunnt want to see my days past that fast...
Describe "wrong time". Is it wrong after boot by a fixed amount, and after correction it stays good till next boot? How much is it wrong? Or does it run fast, or slow, and by what amount?
Please give details.
Particularly, is it off by the difference between your local time and GMT? If so, you made a configuration error when you chose your hardware clock error.
I did not have internet connecting in my opensuse, so it should not be able to know the GMT. 11.1 would process about 12 hours or less after each time I booted into it. and it would change the BIOS time. I think the post here got the same problem:
http://forums.opensuse.org/install-boot-login/409256-time-set-incorrectly-bo...
Hi vsu,
For reference, please show me your /etc/fstab.
If you have a separate partition for /usr, it may cause time problem.
Best,
???? What does fstab have to do with time and why would /usr on a different partition cause problems? -- Use OpenOffice.org http://www.openoffice.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday, 2009-03-15 at 07:43 -0400, James Knott wrote:
What does fstab have to do with time and why would /usr on a different partition cause problems?
Because /etc/localtime maybe a symlink to a file in /usr/share/zoneinfo/somewhere. YaST makes a copy of the file, but sometimes something else makes a symlink instead, and thus it is not accesable when the clock script runs during boot. (See Bug 426270 and Bug 473743) - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkm9A7cACgkQtTMYHG2NR9Ug4QCfSMv+hnFD+o6tiymRfVyNkF0u yRsAmwdYg7syHhqIykDh4/ANeVzximwY =aDsY -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday, 2009-03-15 at 10:05 +0800, vsu wrote:
Particularly, is it off by the difference between your local time and GMT? If so, you made a configuration error when you chose your hardware clock error.
I did not have internet connecting in my opensuse, so it should not be able to know the GMT.
Huh? There is no relation between both. What we asked is if your error is exactly 8 hours, ie, the difference between your local time and UTC aka GMT time.
11.1 would process about 12 hours or less after each time I booted into it. and it would change the BIOS time.
Please clarify, I don't understand this sentence.
I think the post here got the same problem: http://forums.opensuse.org/install-boot-login/409256-time-set-incorrectly-bo...
Please give the output of these commands: grep -i HWCLOCK /etc/sysconfig/* ls /etc/init.d/*clock* chkconfig boot.getclock ; chkconfig boot.clock ; chkconfig ntp hwclock --show ; date --rfc-3339=seconds ; date --rfc-3339=seconds --utc - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkm8cdYACgkQtTMYHG2NR9VZLQCdGS84PgHdJ9Nm5f/FMIugymV5 cdAAn2RxZwjGaDaeVamaCm8G8EX5rwtd =AHEI -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday, 2009-03-15 at 04:11 +0100, I wrote:
Please give the output of these commands:
grep -i HWCLOCK /etc/sysconfig/*
I forgot, and: grep -i timezone= /etc/sysconfig/* - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkm8cu8ACgkQtTMYHG2NR9V65QCfS1tDMHxGNzxM6fkMQEhMaYsx kQ8Anix8fLHuE5ZPADdpV6BR7ZHQEB7v =KD4A -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Please give the output of these commands:
grep -i HWCLOCK /etc/sysconfig/*
I forgot, and:
grep -i timezone= /etc/sysconfig/*
- -- Cheers, Carlos E. R. grep -i HWCLOCK /etc/sysconfig/* Output is: /etc/sysconfig/clock:HWCLOCK="--localtime
grep -i timezone /etc/sysconfig/* Output is: /etc/sysconfig/clock:## Description: Information about your timezone and time /etc/sysconfig/clock:# Timezone (e.g. CET) /etc/sysconfig/clock:TIMEZONE="Asia/Beijing" /etc/sysconfig/clock:DEFAULT_TIMEZONE="US/Eastern" -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
vsu wrote:
Please give the output of these commands:
grep -i HWCLOCK /etc/sysconfig/*
I forgot, and:
grep -i timezone= /etc/sysconfig/*
- -- Cheers, Carlos E. R. grep -i HWCLOCK /etc/sysconfig/* Output is: /etc/sysconfig/clock:HWCLOCK="--localtime
grep -i timezone /etc/sysconfig/* Output is: /etc/sysconfig/clock:## Description: Information about your timezone and time /etc/sysconfig/clock:# Timezone (e.g. CET) /etc/sysconfig/clock:TIMEZONE="Asia/Beijing" /etc/sysconfig/clock:DEFAULT_TIMEZONE="US/Eastern"
I don't know which version of opensuse you are running but there was at least in 11.0 two services, one to set the system clock from cmos at startup and one to set the cmos clock from system time on shutdown. These services, especially the shutdown one, will only work properly with a functioning ntp service. Another possibility your timezone is UTC +8 therefore if your cmos clock (computer hw clock) is set to local time and is correct and suse displays 8 hours ahead then regardless of what your sysconfig says the clock displaying the wrong time thinks the hardware clock is set to UTC time and is adding 8 hours to the time. Is this problem a gui clock problem? Regards Dave P -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday, 2009-03-15 at 13:24 +0200, Dave Plater wrote:
I don't know which version of opensuse you are running but there was at least in 11.0 two services, one to set the system clock from cmos at startup and one to set the cmos clock from system time on shutdown. These services, especially the shutdown one, will only work properly with a functioning ntp service.
No, ntp is not needed. However, the system time should be correct when the system stops, or the system will boot with an incorrect clock next time. The script /etc/init.d/boot.clock does the start/restart part, and runs early, after the root filesystem has been checked, and before the rest for the partitions has been checked - ie, between boot.rootfsck and boot.localfs: S03boot.rootfsck S04boot.clock ... S13boot.getclock (does nothing) The script /etc/init.d/boot.getclock does the stop part, and runs also early in the stop sequence (instead of late, as K18boot.clock does) K09boot.getclock ... K11boot.localfs ... K18boot.clock (does nothing) That's the reason there are two different scripts: the system needs to setup the clock correctly very soon, before mounting r/w the filesystem, and when halting, needs to run also early, at least before the filesystem is umounted (because it writes to /etc/adjtime). Notice that K11boot.localfs runs earlier than K18boot.clock, so the "stop" section of the script can not be used. http://lists.opensuse.org/opensuse-factory/2008-06/msg00666.html - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkm9cX8ACgkQtTMYHG2NR9VxVQCbBczGqJyYacl1hQldaRr/qKys El0An0rewrzbKmdGtWwvLB2x1JIPuG2Z =/duJ -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday, 2009-03-16 at 10:42 +0800, vsu wrote:
grep -i HWCLOCK /etc/sysconfig/* Output is: /etc/sysconfig/clock:HWCLOCK="--localtime
grep -i timezone /etc/sysconfig/* Output is: /etc/sysconfig/clock:## Description: Information about your timezone and time /etc/sysconfig/clock:# Timezone (e.g. CET) /etc/sysconfig/clock:TIMEZONE="Asia/Beijing" /etc/sysconfig/clock:DEFAULT_TIMEZONE="US/Eastern"
I asked for more info than that, please do: grep -i HWCLOCK /etc/sysconfig/* grep -i timezone= /etc/sysconfig/* ls /etc/init.d/*clock* chkconfig boot.getclock ; chkconfig boot.clock ; chkconfig ntp hwclock --show ; date --rfc-3339=seconds ; date --rfc-3339=seconds --utc ls -l /etc/localtime - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkm9BFkACgkQtTMYHG2NR9XvDgCghcnFCyoRnoJa9wc0oFNJVdjV 9mcAniFyvscukTdy8Q956zB+zyOKqRrW =L7Jh -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (8)
-
Boyd Stephen Smith Jr. -
Carlos E. R. -
Ciro Iriarte -
Dave Plater -
James Knott -
Matt Hayes -
Satoru Matsumoto -
vsu