[opensuse] set "local time" in openSUSE 12.2 sticky (was: couple of 12.2 surprises)
2012. szeptember 7. 5:38 napon Carl Fletcher <caf4926@gmail.com> írta:
On 06/09/12 13:44, Basil Chupin wrote:
you did not set Windows to auto adjust for daylight saving time This is nothing whatsoever to do with it.
The behaviour is: Where a Windows OS is present, during install the section where you set UTC or not usually would have UTC unchecked (That is it understands that Windows is present). In 12.2 it doesn't, the UTC is checked. If you uncheck it, it warns you that you do not have Windows installed and are you sure...? blah blah... If you configure with UTC unchecked, post install you will find the installer has re-applied UTC and check is back. If you use Yast to configure NTP to manage time and uncheck UTC, it gives the same warning about not having Windows.
This behaviour is all wrong and different to previous versions 12.1 11.4 etc....
Hello: I think the time should be set as the user chooses, independently from whether he has Windows or not. I have installed oS 12.1 and set time to "local" as I always did before in previous openSUSE/SUSE versions. At next boot my time was set back to UTC. I went to YaST and set it back to local. After next boot it was again UTC. At every reboot the time is set back to UTC. How can I set "local time" permanently? I don't have windows. (Please do not ask why I want local time and explain why UTC is better.) Thanks, Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2012-09-08 12:04, Istvan Gabor wrote:
How can I set "local time" permanently? I don't have windows.
Edit /etc/adjtime and put local there. And before somebody asks, it was reported in time on bugzilla.
(Please do not ask why I want local time and explain why UTC is better.)
The fact is you should not be using local, regardless your preferences in this. :-P - -- - -- Cheers / Saludos, Carlos E. R. (from 11.4 x86_64 "Celadon" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iF4EAREIAAYFAlBLG7gACgkQja8UbcUWM1xaxwEAnBk1ZxrlrgILvRbL8F41yP9M NMhQ0OMxPsaHEONJtXIBAJ81RKGFCmNnLus8wUML/u4FE49rg1gAmwA635QjXjbN =Jt5v -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 2012-09-08 12:04, Istvan Gabor wrote:
How can I set "local time" permanently? I don't have windows.
Edit /etc/adjtime and put local there. And before somebody asks, it was reported in time on bugzilla.
My brandnew 12.2 system doesn't have /etc/adjtime, but it looks it is created when you do "hwclock --systohc". Init-script boot.clock normally would do that, but afaict it isn't part of the init-sequence. Doesn't look like systemd takes care of it either, but I'm no expert. -- Per Jessen, Zürich (17.6°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2012-09-08 12:37, Per Jessen wrote:
Carlos E. R. wrote:
Edit /etc/adjtime and put local there. And before somebody asks, it was reported in time on bugzilla.
My brandnew 12.2 system doesn't have /etc/adjtime, but it looks it is created when you do "hwclock --systohc".
Do "hwclock --systohc --localtime" instead
Init-script boot.clock normally would do that, but afaict it isn't part of the init-sequence. Doesn't look like systemd takes care of it either, but I'm no expert.
I have forgotten the details, but the thing is the logic has been changed. Previously there was some logic to adjust the cmos clock for drift while powered off, by adding or subtracting some interval when setting the clock on every boot. This was a cause of problems when the cmos is set to local time and Windows has been booted in between (hey! my clock is two hours off on every boot!), so the logic has been disabled entirely if you use "local", it is only used for "utc". So far, good. As a side effect, they thought that /etc/adjtime (the file that stores the drift adjustment) is no longer needed and is not created if you use local - but this has undesired effects. - -- Cheers / Saludos, Carlos E. R. (from 11.4 x86_64 "Celadon" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iF4EAREIAAYFAlBLJbsACgkQja8UbcUWM1yAWgD6AwsIndY7GPdf+fu84UKE6Gqm Il8DUxQCIuR3GQTeqMUA/j3iCcMcYek80qJrihCYCKeyWG0QUFcDAmHiK3Dqpt0g =xEtO -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 2012-09-08 12:37, Per Jessen wrote:
Carlos E. R. wrote:
Edit /etc/adjtime and put local there. And before somebody asks, it was reported in time on bugzilla.
My brandnew 12.2 system doesn't have /etc/adjtime, but it looks it is created when you do "hwclock --systohc".
Do "hwclock --systohc --localtime" instead
Init-script boot.clock normally would do that, but afaict it isn't part of the init-sequence. Doesn't look like systemd takes care of it either, but I'm no expert.
I have forgotten the details, but the thing is the logic has been changed. Previously there was some logic to adjust the cmos clock for drift while powered off, by adding or subtracting some interval when setting the clock on every boot. This was a cause of problems when the cmos is set to local time and Windows has been booted in between (hey! my clock is two hours off on every boot!), so the logic has been disabled entirely if you use "local", it is only used for "utc".
So far, good.
As a side effect, they thought that /etc/adjtime (the file that stores the drift adjustment) is no longer needed and is not created if you use local - but this has undesired effects.
I guess /etc/adjtime isnt needed when you use NTP (the default). -- Per Jessen, Zürich (18.6°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2012-09-08 13:11, Per Jessen wrote:
I guess /etc/adjtime isnt needed when you use NTP (the default).
Yes, you need it, because some other system script check for it and fail. It is the reason behind the problem of "local" hot holding in yast. - -- Cheers / Saludos, Carlos E. R. (from 11.4 x86_64 "Celadon" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iF4EAREIAAYFAlBLVNwACgkQja8UbcUWM1yY3gD+NUhf6bLC+JXakgl0SXdpOkTM u/AFcKHqtiACtkq7v8ABAINWnKQYpls6IXpnZZL7gL1IxB15cW4PUubg2Zc1Zf0s =z84s -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 2012-09-08 13:11, Per Jessen wrote:
I guess /etc/adjtime isnt needed when you use NTP (the default).
Yes, you need it, because some other system script check for it and fail. It is the reason behind the problem of "local" hot holding in yast.
Hmm, not sure I understand - when you're using NTP, your time is running in UTC. A new 12.2 system doesn't have /etc/adjtime, like I described yesterday. I see no complaints in the logs. Anyway, it's not important, I was just curious. -- Per Jessen, Zürich (15.6°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2012-09-09 09:27, Per Jessen wrote:
Carlos E. R. wrote:
On 2012-09-08 13:11, Per Jessen wrote:
I guess /etc/adjtime isnt needed when you use NTP (the default).
Yes, you need it, because some other system script check for it and fail. It is the reason behind the problem of "local" hot holding in yast.
Hmm, not sure I understand - when you're using NTP, your time is running in UTC. A new 12.2 system doesn't have /etc/adjtime, like I described yesterday. I see no complaints in the logs. Anyway, it's not important, I was just curious.
There are reports of problems when that file is missing. There shouldn't be problems, but there are. I don't have the bug reference where they talk about why not create adjtime if time is local, and why it is seen that the file is needed. I don't remember offhand what the problems were, perhaps it was that yast thinks that the cmos is set to utc. - -- Cheers / Saludos, Carlos E. R. (from 11.4 x86_64 "Celadon" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iF4EAREIAAYFAlBM514ACgkQja8UbcUWM1ztFQEAgEQl71ka/9rbYrokLisrpjo4 EcCdpvl937QqyhelObIA/1hQmZ8QxVbuJyix3zYO8ERF1IIeWwduG2M0cmA0ppSU =naoM -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 2012-09-09 09:27, Per Jessen wrote:
Carlos E. R. wrote:
On 2012-09-08 13:11, Per Jessen wrote:
I guess /etc/adjtime isnt needed when you use NTP (the default).
Yes, you need it, because some other system script check for it and fail. It is the reason behind the problem of "local" hot holding in yast.
Hmm, not sure I understand - when you're using NTP, your time is running in UTC. A new 12.2 system doesn't have /etc/adjtime, like I described yesterday. I see no complaints in the logs. Anyway, it's not important, I was just curious.
There are reports of problems when that file is missing. There shouldn't be problems, but there are. I don't have the bug reference where they talk about why not create adjtime if time is local, and why it is seen that the file is needed.
On a newly upgraded 12.2 server, I saw this message in the log: ntp[3579]: hwclock: With --noadjfile, you must specify either --utc or --localtime At this point, /etc/adjtime _did_ exist. Then I deleted it, and rebooted, same message. I think that init-script needs a closer look. -- Per Jessen, Zürich (22.0°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2012-09-10 11:58, Per Jessen wrote:
Carlos E. R. wrote:
There are reports of problems when that file is missing. There shouldn't be problems, but there are. I don't have the bug reference where they talk about why not create adjtime if time is local, and why it is seen that the file is needed.
On a newly upgraded 12.2 server, I saw this message in the log:
ntp[3579]: hwclock: With --noadjfile, you must specify either --utc or --localtime
At this point, /etc/adjtime _did_ exist. Then I deleted it, and rebooted, same message.
I think that init-script needs a closer look.
Check if that file contains the utc or local line. If it doesn't, you have to recreate the file with --localtime: "hwclock --systohc --localtime". Or with zeroes: echo "0.0 0 0.0" > /etc/adjtime echo "0" >> /etc/adjtime echo "LOCAL" >> /etc/adjtime as explained in <https://bugzilla.novell.com/show_bug.cgi?id=450196#c93> - -- Cheers / Saludos, Carlos E. R. (from 11.4 x86_64 "Celadon" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iF4EAREIAAYFAlBNvd0ACgkQja8UbcUWM1zFvwD/SUN0E+TFj8Tiot3TWU3+WiCt gHPJBgu2zqRLbKgjMCMA/3w8eiasXCe0W7iGjzxpSwTtBmMIDqLxUfYk/G9TEA2m =XWZD -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Carlos E. R. wrote:
On 2012-09-10 11:58, Per Jessen wrote:
Carlos E. R. wrote:
There are reports of problems when that file is missing. There shouldn't be problems, but there are. I don't have the bug reference where they talk about why not create adjtime if time is local, and why it is seen that the file is needed.
On a newly upgraded 12.2 server, I saw this message in the log:
ntp[3579]: hwclock: With --noadjfile, you must specify either --utc or --localtime
At this point, /etc/adjtime _did_ exist. Then I deleted it, and rebooted, same message.
I think that init-script needs a closer look.
Check if that file contains the utc or local line. If it doesn't, you have to recreate the file with --localtime: "hwclock --systohc --localtime". Or with zeroes:
Well no, I don't need it, all my systems run with NTP in UTC :-) -- Per Jessen, Zürich (22.7°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2012-09-10 12:26, Per Jessen wrote:
Carlos E. R. wrote:
Check if that file contains the utc or local line. If it doesn't, you have to recreate the file with --localtime: "hwclock --systohc --localtime". Or with zeroes:
Well no, I don't need it, all my systems run with NTP in UTC :-)
Ah, then change the line to "--utc" instead. The point is having that word in the adjtime file. - -- Cheers / Saludos, Carlos E. R. (from 11.4 x86_64 "Celadon" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iF4EAREIAAYFAlBNxRcACgkQja8UbcUWM1zdhgD+Iz3/YBNHwE245en5OrKT97pP 9wtEowlQEZKuHrKOZxkA/2UNdDoE/9JPgTjqwRIy3K39rpD7kU/5UlWlv0yGGEAC =Lmx3 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 2012-09-10 12:26, Per Jessen wrote:
Carlos E. R. wrote:
Check if that file contains the utc or local line. If it doesn't, you have to recreate the file with --localtime: "hwclock --systohc --localtime". Or with zeroes:
Well no, I don't need it, all my systems run with NTP in UTC :-)
Ah, then change the line to "--utc" instead. The point is having that word in the adjtime file.
Probably, but like I said, I just deleted the file. -- Per Jessen, Zürich (25.3°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Mon, Sep 10, 2012 at 11:58:00AM +0200, Per Jessen wrote:
Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 2012-09-09 09:27, Per Jessen wrote:
Carlos E. R. wrote:
On 2012-09-08 13:11, Per Jessen wrote:
I guess /etc/adjtime isnt needed when you use NTP (the default).
Yes, you need it, because some other system script check for it and fail. It is the reason behind the problem of "local" hot holding in yast.
Hmm, not sure I understand - when you're using NTP, your time is running in UTC. A new 12.2 system doesn't have /etc/adjtime, like I described yesterday. I see no complaints in the logs. Anyway, it's not important, I was just curious.
There are reports of problems when that file is missing. There shouldn't be problems, but there are. I don't have the bug reference where they talk about why not create adjtime if time is local, and why it is seen that the file is needed.
On a newly upgraded 12.2 server, I saw this message in the log:
ntp[3579]: hwclock: With --noadjfile, you must specify either --utc or --localtime
At this point, /etc/adjtime _did_ exist. Then I deleted it, and rebooted, same message.
I think that init-script needs a closer look.
Do not use --noadjfile Werner -- "Having a smoking section in a restaurant is like having a peeing section in a swimming pool." -- Edward Burr -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Dr. Werner Fink wrote:
On Mon, Sep 10, 2012 at 11:58:00AM +0200, Per Jessen wrote:
Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 2012-09-09 09:27, Per Jessen wrote:
Carlos E. R. wrote:
On 2012-09-08 13:11, Per Jessen wrote:
I guess /etc/adjtime isnt needed when you use NTP (the default).
Yes, you need it, because some other system script check for it and fail. It is the reason behind the problem of "local" hot holding in yast.
Hmm, not sure I understand - when you're using NTP, your time is running in UTC. A new 12.2 system doesn't have /etc/adjtime, like I described yesterday. I see no complaints in the logs. Anyway, it's not important, I was just curious.
There are reports of problems when that file is missing. There shouldn't be problems, but there are. I don't have the bug reference where they talk about why not create adjtime if time is local, and why it is seen that the file is needed.
On a newly upgraded 12.2 server, I saw this message in the log:
ntp[3579]: hwclock: With --noadjfile, you must specify either --utc or --localtime
At this point, /etc/adjtime _did_ exist. Then I deleted it, and rebooted, same message.
I think that init-script needs a closer look.
Do not use --noadjfile
Which is exactly what /etc/init.d/ntp does. -- Per Jessen, Zürich (24.3°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Tue, Sep 11, 2012 at 02:33:03PM +0200, Per Jessen wrote:
Dr. Werner Fink wrote:
On Mon, Sep 10, 2012 at 11:58:00AM +0200, Per Jessen wrote:
Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 2012-09-09 09:27, Per Jessen wrote:
Carlos E. R. wrote:
On 2012-09-08 13:11, Per Jessen wrote:
> I guess /etc/adjtime isnt needed when you use NTP (the default).
Yes, you need it, because some other system script check for it and fail. It is the reason behind the problem of "local" hot holding in yast.
Hmm, not sure I understand - when you're using NTP, your time is running in UTC. A new 12.2 system doesn't have /etc/adjtime, like I described yesterday. I see no complaints in the logs. Anyway, it's not important, I was just curious.
There are reports of problems when that file is missing. There shouldn't be problems, but there are. I don't have the bug reference where they talk about why not create adjtime if time is local, and why it is seen that the file is needed.
On a newly upgraded 12.2 server, I saw this message in the log:
ntp[3579]: hwclock: With --noadjfile, you must specify either --utc or --localtime
At this point, /etc/adjtime _did_ exist. Then I deleted it, and rebooted, same message.
I think that init-script needs a closer look.
Do not use --noadjfile
Which is exactly what /etc/init.d/ntp does.
Which is a bug. Werner -- "Having a smoking section in a restaurant is like having a peeing section in a swimming pool." -- Edward Burr -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sun, Sep 09, 2012 at 09:27:44AM +0200, Per Jessen wrote:
Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 2012-09-08 13:11, Per Jessen wrote:
I guess /etc/adjtime isnt needed when you use NTP (the default).
Yes, you need it, because some other system script check for it and fail. It is the reason behind the problem of "local" hot holding in yast.
Hmm, not sure I understand - when you're using NTP, your time is running in UTC. A new 12.2 system doesn't have /etc/adjtime, like I described yesterday. I see no complaints in the logs. Anyway, it's not important, I was just curious.
This is a bug as at least YaST country module should write out an initial /etc/adjtime Werner -- "Having a smoking section in a restaurant is like having a peeing section in a swimming pool." -- Edward Burr -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sat, Sep 08, 2012 at 01:11:27PM +0200, Per Jessen wrote:
Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 2012-09-08 12:37, Per Jessen wrote:
Carlos E. R. wrote:
Edit /etc/adjtime and put local there. And before somebody asks, it was reported in time on bugzilla.
My brandnew 12.2 system doesn't have /etc/adjtime, but it looks it is created when you do "hwclock --systohc".
Do "hwclock --systohc --localtime" instead
Init-script boot.clock normally would do that, but afaict it isn't part of the init-sequence. Doesn't look like systemd takes care of it either, but I'm no expert.
I have forgotten the details, but the thing is the logic has been changed. Previously there was some logic to adjust the cmos clock for drift while powered off, by adding or subtracting some interval when setting the clock on every boot. This was a cause of problems when the cmos is set to local time and Windows has been booted in between (hey! my clock is two hours off on every boot!), so the logic has been disabled entirely if you use "local", it is only used for "utc".
So far, good.
As a side effect, they thought that /etc/adjtime (the file that stores the drift adjustment) is no longer needed and is not created if you use local - but this has undesired effects.
I guess /etc/adjtime isnt needed when you use NTP (the default).
On 12.2, tjhat is with latest hwclock and systemd the /etc/adjtime is the reference of having LOCAL or UTC reference time in CMOS. For adjusting the CMOS drift, the option --adjust is required. Using LOCAL as reference without hard requirement is broken but OK if the user is willingly to correct the day light switches twice a year before the file systems are checked and mounted. Werner -- "Having a smoking section in a restaurant is like having a peeing section in a swimming pool." -- Edward Burr -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
2012. szeptember 8. 12:37 napon Per Jessen <per@computer.org> írta:
Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 2012-09-08 12:04, Istvan Gabor wrote:
How can I set "local time" permanently? I don't have windows.
Edit /etc/adjtime and put local there. And before somebody asks, it was reported in time on bugzilla.
My brandnew 12.2 system doesn't have /etc/adjtime, but it looks it is created when you do "hwclock --systohc".
Init-script boot.clock normally would do that, but afaict it isn't part of the init-sequence. Doesn't look like systemd takes care of it either, but I'm no expert.
I have created /etc/adjtime using "hwclock --systohc" and added "LOCAL" to the 3rd line (replaced UTC by LOCAL). After this my system clock was set to 2 hours late (after reboot). I tried to use sntp to change system time as I always did previously: # sntp -j ntp1.ptb.de which gave Time not set: adjtime(): Invalid argument error. Then I tried # sntp -s ntp1.ptb.de which worked. Since then "sntp -j" works too, I can not reproduce the error. Anyway it seems that it's working now. Thank you for your help. Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
2012. szeptember 8. 12:19 napon "Carlos E. R." <carlos.e.r@opensuse.org> írta:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 2012-09-08 12:04, Istvan Gabor wrote:
How can I set "local time" permanently? I don't have windows.
Edit /etc/adjtime and put local there. And before somebody asks, it was reported in time on bugzilla.
I did. I do not follow factory list regularly. [ But; Just a general remark, not addressed to you personally: If it was reported in time why wasn't it fixed in time too? All the last 3-4 openSUSE releases came out with some serious bugs, unfortunately. ] Thanks, Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2012-09-08 19:59, Istvan Gabor wrote:
If it was reported in time why wasn't it fixed in time too?
Can't say, the issue is still under debate AFAIK. - -- Cheers / Saludos, Carlos E. R. (from 11.4 x86_64 "Celadon" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iF4EAREIAAYFAlBL3HMACgkQja8UbcUWM1w7awD/X2aScUKrS5jTJLDwF5Qgj+FQ m/rX0wptpy6pAnoo8IEA/37gCsOgwfxAW5ZQtGwdZFd6BjPkOSFZ2zDEi4cPEppO =rEUa -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sun, 09 Sep 2012 02:01:55 +0200 "Carlos E. R." <robin.listas@telefonica.net> wrote: ...
On 2012-09-08 19:59, Istvan Gabor wrote:
If it was reported in time why wasn't it fixed in time too?
Can't say, the issue is still under debate AFAIK.
It is nice that is under debate. We can debate as long as we want, but in the meantime people are installing 12.2 and see clock jumping around. We can give all explanations we want why UTC is better, but that does not make clock working. What impression that leaves? For instance, this computer is desktop that will spend lifetime in the same location. Hardware clock is set to local time and correct time zone is set too. What else is needed to have it work correctly? -- Rajko. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Rajko wrote:
On Sun, 09 Sep 2012 02:01:55 +0200 "Carlos E. R." <robin.listas@telefonica.net> wrote: ...
On 2012-09-08 19:59, Istvan Gabor wrote:
If it was reported in time why wasn't it fixed in time too?
Can't say, the issue is still under debate AFAIK.
It is nice that is under debate.
We can debate as long as we want, but in the meantime people are installing 12.2 and see clock jumping around.
We can give all explanations we want why UTC is better, but that does not make clock working.
What impression that leaves?
For instance, this computer is desktop that will spend lifetime in the same location. Hardware clock is set to local time and correct time zone is set too. What else is needed to have it work correctly?
See Felix Miata's reply to the OP. -- Per Jessen, Zürich (17.8°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2012-09-09 10:14, Rajko wrote:
For instance, this computer is desktop that will spend lifetime in the same location. Hardware clock is set to local time and correct time zone is set too. What else is needed to have it work correctly?
Unless your computer double boots with Windows, there is absolutely no reason whatsoever to use local time in cmos. - -- Cheers / Saludos, Carlos E. R. (from 11.4 x86_64 "Celadon" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iF4EAREIAAYFAlBM5acACgkQja8UbcUWM1yrvwD+O2/HVcC4laZ2g/bgyRmzd4g4 AcjyroP2Cu9zBafaRlIA/jbrL4cWB2WmAhpiW+CfsL4z2HaZLgZE68fmC9aH1Eky =Wwe7 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2012/09/09 20:53 (GMT+0200) Carlos E. R. composed:
Rajko wrote:
For instance, this computer is desktop that will spend lifetime in the same location. Hardware clock is set to local time and correct time zone is set too. What else is needed to have it work correctly?
Unless your computer double boots with Windows, there is absolutely no reason whatsoever to use local time in cmos.
1-Windows and Linux are not the only operating systems multibooters use. 2-To some, multiboot means multiple machines, which work best on a LAN where all connected have synchronized clocks. 3-I really don't care what time it is outside my time zone. So, there are at least five reasons justifying use of local time: 2, [Free,MS,PC] DOS, Windows, OS/2, LAN. Likely there are others. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2012-09-09 21:10, Felix Miata wrote:
On 2012/09/09 20:53 (GMT+0200) Carlos E. R. composed:
Unless your computer double boots with Windows, there is absolutely no reason whatsoever to use local time in cmos.
1-Windows and Linux are not the only operating systems multibooters use.
Ok. That is one reason.
2-To some, multiboot means multiple machines, which work best on a LAN where all connected have synchronized clocks.
I don't see why the LAN would be related to the cmos clock a particular machine has.
3-I really don't care what time it is outside my time zone.
Me neither, that is not relevant to the issue.
So, there are at least five reasons justifying use of local time: 2, [Free,MS,PC] DOS, Windows, OS/2, LAN. Likely there are others.
Only one reason: multiboot. I may add another: virtual machines in vmware. - -- Cheers / Saludos, Carlos E. R. (from 11.4 x86_64 "Celadon" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iF4EAREIAAYFAlBM7KYACgkQja8UbcUWM1xmpgD/VHgasuftDMySU80qBpMMxsQA W0vabRNCe1P9GKZnh3QA/1QlPdcNowbTJZGcCQ0OMJZnfedkU5FxvxBBFYuZ2jWJ =uWA2 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2012/09/09 21:23 (GMT+0200) Carlos E. R. composed:
2-To some, multiboot means multiple machines, which work best on a LAN where all connected have synchronized clocks.
I don't see why the LAN would be related to the cmos clock a particular machine has.
http://fm.no-ip.com/SS/localtime01.png See now? The bottom two files in each pane are triplets. Each pane lists files on different model STBs from the same manufacturer. Each runs Linux, the newer 2.6.22, the elder 2.6.15. "now" on each was created via telnet login. "test" was created on the LAN server and copied to each STB via MC FTP. Each STB displays correct local time on the TV and for file lists displayed via telnet login, makes timer recordings in sync with the programs they were set to record, and sets its clock via NTP. Your challenge is to determine which of the three puters is/are using localtime, and which is/are using UTC for their respective CMOS clocks. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2012-09-09 22:37, Felix Miata wrote:
On 2012/09/09 21:23 (GMT+0200) Carlos E. R. composed:
2-To some, multiboot means multiple machines, which work best on a LAN where all connected have synchronized clocks.
I don't see why the LAN would be related to the cmos clock a particular machine has.
http://fm.no-ip.com/SS/localtime01.png
See now? The bottom two files in each pane are triplets. Each pane lists files on different model STBs from the same manufacturer. Each runs Linux, the newer 2.6.22, the elder 2.6.15. "now" on each was created via telnet login. "test" was created on the LAN server and copied to each STB via MC FTP. Each STB displays correct local time on the TV and for file lists displayed via telnet login, makes timer recordings in sync with the programs they were set to record, and sets its clock via NTP. Your challenge is to determine which of the three puters is/are using localtime, and which is/are using UTC for their respective CMOS clocks.
But I do not care what other computers over the network are using for their cmos clock, if they have them! It is absolutely of no relevance. - -- Cheers / Saludos, Carlos E. R. (from 11.4 x86_64 "Celadon" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iF4EAREIAAYFAlBNF4MACgkQja8UbcUWM1yjpwD8CPN3/45Nu5a9Xm3Uns6NSe+0 6E+Jdr8Oi+aN5LsHaR8A/jxDB5dquYNyuJGf2m+t7eJ7Ao4krz1kFFY8HI8QRaYs =pdzl -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Istvan Gabor wrote:
I have installed oS 12.1 and set time to "local" as I always did before in previous openSUSE/SUSE versions. At next boot my time was set back to UTC. I went to YaST and set it back to local. After next boot it was again UTC. At every reboot the time is set back to UTC.
How can I set "local time" permanently? I don't have windows. (Please do not ask why I want local time and explain why UTC is better.)
Maybe a stupid question, but when you say you set time to "local", do you mean you untick the Yast->System->Date and Time: "Hardware clock is UTC" box ? -- Per Jessen, Zürich (17.5°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
2012. szeptember 8. 12:27 napon Per Jessen <per@computer.org> írta:
Istvan Gabor wrote:
I have installed oS 12.1 and set time to "local" as I always did before in previous openSUSE/SUSE versions. At next boot my time was set back to UTC. I went to YaST and set it back to local. After next boot it was again UTC. At every reboot the time is set back to UTC.
How can I set "local time" permanently? I don't have windows. (Please do not ask why I want local time and explain why UTC is better.)
Maybe a stupid question, but when you say you set time to "local", do you mean you untick the Yast->System->Date and Time: "Hardware clock is UTC" box ?
Yes. I untick that box. After reboot it is ticked back. Thanks. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
2012. szeptember 8. 12:27 napon Per Jessen <per@computer.org> írta:
Istvan Gabor wrote:
I have installed oS 12.1 and set time to "local" as I always did before in previous openSUSE/SUSE versions. At next boot my time was set back to UTC. I went to YaST and set it back to local. After next boot it was again UTC. At every reboot the time is set back to UTC.
How can I set "local time" permanently? I don't have windows. (Please do not ask why I want local time and explain why UTC is better.)
Maybe a stupid question, but when you say you set time to "local", do you mean you untick the Yast->System->Date and Time: "Hardware clock is UTC" box ?
Yes. I untick that box. After reboot it is ticked back. Thanks. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2012/09/08 12:04 (GMT+0200) Istvan Gabor composed:
How can I set "local time" permanently? I don't have windows. (Please do not ask why I want local time and explain why UTC is better.)
https://bugzilla.novell.com/show_bug.cgi?id=450196#c93 -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (7)
-
Carlos E. R. -
Carlos E. R. -
Dr. Werner Fink -
Felix Miata -
Istvan Gabor -
Per Jessen -
Rajko