Re: [opensuse] Extrange change in "/etc/sysconfig/clock"
On 2013-08-31 22:09, James Knott wrote:
Carlos E. R. wrote:
The cure on those cases was to set the system clock manually, transfer contents to cmos clock, and then erase the adjtime file, in the knowledge that rebooting would set it up correctly.
The cure is to not let Windows change the hardware clock. Let Linux do it, but with the clock set to local time, instead of the usual UTC.
Few people know how to forbid Windows to change the "hardware clock". I don't. By the way, if you set the cmos clock to "local", openSUSE will refuse to do the yearly summer/winter change, and other adjustments to the cmos clock (aka bios clock, aka "hardware clock). On the other hand, on windows 7/8 (and vista, I think) it is possible to tell Windows to use the cmos clock as UTC instead of local. This is what I use and since them, I have no problems. But even if you do any of those solutions, the /etc/adjtime file is already corrupted (if you have the hours shift problem on boot). You have to remove it and recreate it again. -- Cheers / Saludos, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Carlos E. R. wrote:
Few people know how to forbid Windows to change the "hardware clock". I don't.
The way to do it is: a) don't manually change it and 2) do not enable "Internet Time" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with SeaMonkey - http://www.enigmail.net/ iF4EAREIAAYFAlIicasACgkQAtgmQnSY2k3uYwD+Iu5b5ZPoBIZuMf3AXPI6UWkz GU5awl1d2VjnGyJOCZwBAMUAI2odu7Sz0zkQVG/Vtjijvtz3pmsCN74P/oKSgOx+ =DdhF -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Saturday, 2013-08-31 at 18:43 -0400, James Knott wrote:
Carlos E. R. wrote:
Few people know how to forbid Windows to change the "hardware clock". I don't.
The way to do it is:
a) don't manually change it and 2) do not enable "Internet Time"
Well... it might work. It is not a "prohibition", it is just that Windows does not need to adjust it. But it may do so, anyway. It will on summer/winter hour change, for example. And anyways, that may help the people reading this now, but not those that come asking us for help after their clock is going wrong on every boot. - -- Cheers, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iEYEARECAAYFAlIilU4ACgkQtTMYHG2NR9VobwCfa/5/FIxt3aDpJYw+JbSLGF+I dkMAn223cjcI+ZcCFaE10g7NKVBNO6IH =AebW -----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:
Well... it might work. It is not a "prohibition", it is just that Windows does not need to adjust it. But it may do so, anyway. It will on summer/winter hour change, for example.
It's never been a problem for me, but there is also a setting to not allow it to adjust for time changes. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sat, 31 Aug 2013 23:03:03 Carlos E. R. wrote:
On 2013-08-31 22:09, James Knott wrote:
Carlos E. R. wrote:
The cure on those cases was to set the system clock manually, transfer contents to cmos clock, and then erase the adjtime file, in the knowledge that rebooting would set it up correctly.
The cure is to not let Windows change the hardware clock. Let Linux do it, but with the clock set to local time, instead of the usual UTC.
Few people know how to forbid Windows to change the "hardware clock". I don't.
By the way, if you set the cmos clock to "local", openSUSE will refuse to do the yearly summer/winter change, and other adjustments to the cmos clock (aka bios clock, aka "hardware clock).
Huh? Since when? I have never had my CMOS clock running UTC - always local - and the winter/summer time change happens automatically on the correct date/time every October and April.
On the other hand, on windows 7/8 (and vista, I think) it is possible to tell Windows to use the cmos clock as UTC instead of local. This is what I use and since them, I have no problems.
No 'doze on this box (except in a Virtualbox VM) or its predecessors for many years. I do, however, have a couple of laptops with dual-boot openSuSE/Windows and run a mixed lan with openSuSE and Windows 7 machines and even the occasional Vista and XP guest and I've never had a clock problem, most likely because all have always run the hardware clock on local time. Quite frankly, I've never had an adequate explanation of why it would be more desirable to run the hardware clock at UTC.
But even if you do any of those solutions, the /etc/adjtime file is already corrupted (if you have the hours shift problem on boot). You have to remove it and recreate it again.
-- ============================================================== Rodney Baker VK5ZTV rodney.baker@iinet.net.au ============================================================== -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Rodney Baker wrote:
Quite frankly, I've never had an adequate explanation of why it would be more desirable to run the hardware clock at UTC.
From a user perspective, it would likely mean no difference. But it's better to offset from the standard for local needs. Don't forget, Unix originated in the telecom world, where UTC is the standard. It was also used in scientific areas, including astronomy, where again UTC is generally used. So, UTC is the reference for everyone, who then adjust for local use as necessary. Also, IIRC, Linux & Unix time stamps are in UTC to avoid the ambiguity that occurs when using local time stamps.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday, 2013-09-01 at 23:56 +0930, Rodney Baker wrote:
On Sat, 31 Aug 2013 23:03:03 Carlos E. R. wrote:
By the way, if you set the cmos clock to "local", openSUSE will refuse to do the yearly summer/winter change, and other adjustments to the cmos clock (aka bios clock, aka "hardware clock).
Huh? Since when? I have never had my CMOS clock running UTC - always local - and the winter/summer time change happens automatically on the correct date/time every October and April.
A message when installing, I think, says so. It appeared with 12.3, I think. Here is one (/etc/sysconfig/clock): ## Description: Correct systematic drift of the HW clock ## Type: list(yes,no,) # # Add or subtract time from the Hardware Clock to account for # systematic drift since the last time the clock was set or # adjusted. By default off as this can cause trouble. For # systems using localtime for HW clock this will ignored. # USE_ADJUST="no" But there are more.
Quite frankly, I've never had an adequate explanation of why it would be more desirable to run the hardware clock at UTC.
I have, many times, so I will not repeat them :-) - -- Cheers, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iEYEARECAAYFAlIjWTEACgkQtTMYHG2NR9Un1QCgiaDQR33KNWrEVpcZof5bIPHy nPEAnA3tQa31d3gaPF8gSlQ2pSj2pfKJ =MUMr -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (3)
-
Carlos E. R.
-
James Knott
-
Rodney Baker