Re: [opensuse] Time Issues 11.3
On 08/26/2010 05:00 PM, DenverD wrote:
Thanks for the information, I've been using Linux for 4 years, so guess a intermediate have a lot to learn still. Anyhow I tried the suggestion above prior to making my post, and tried setting hw clock to UTC and I still have a 1 hour diff, regardless if hwclock is set to local or UTC. Another words system clock is always set to 1 hour off regardless if hwclock is local or UTC. For now only way system clock is correct, is I have set the hwclock to one hour off, then when system clock is set it works. I'm open to ideas. Thanks, Tony -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Tony wrote:
I'm open to ideas. NTP.
Configure the computer to use an NTP server, to get the correct time. Linux always runs NTP at boot and periodically afterwards. You can also set Windows to use NTP and also to not change the time for standard/daylight savings times. IIRC, Windows sets the hardware clock on time change, whereas Linux changes the offset and leaves the hardware clock alone. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 2010-08-29 22:19, Tony wrote:
It does not matter how you set it up, local or utc. Linux can handle both. However, after you change the settings (in YaST) and set up the clock, you have to delete the "/etc/adjtime" file (it will be recreated). To avoid problems with how the desktop might handle the clock, manipulate it on an xterm, as root ("su -", the dash is important), with the command "date". -- Cheers / Saludos, Carlos E. R. (from 11.2 x86_64 "Emerald" GM (Elessar))
On Mon, Aug 30, 2010 at 02:55:04AM +0200, Carlos E. R. wrote:
This suggestion is misleading and not needed. Please follow the advice given by James in this thread. That's the correct way to address your issue. Lars -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2010-08-31 13:09, Lars Müller wrote:
This suggestion is proper and proven.
Please follow the advice given by James in this thread. That's the correct way to address your issue.
Please follow my advice. Please be polite and prove your point. You are as Suse employee and should know better than blatantly disregard advices like that. :-/ - -- Cheers / Saludos, Carlos E. R. (from 11.2 x86_64 "Emerald" GM (Elessar)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAkx853UACgkQU92UU+smfQUAwACgg97P6QFekOv9JCaZf77gopU5 frkAniYTFv3fbomHIN4aolCm3ynMy+Mm =4Ru5 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tue, Aug 31, 2010 at 01:28:53PM +0200, Carlos E. R. wrote:
It is not as this might lead to non continous time changes. That's why running ntpd on a host all the time compared to calling ntpdate called by cron is of advantage.
Hey, your advice is not the correct way to address time issues. That's it. There is nothing to add as James already gave the correct instructions. EOT Lars -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2010-08-31 13:37, Lars Müller wrote:
On Tue, Aug 31, 2010 at 01:28:53PM +0200, Carlos E. R. wrote:
Calling ntpd is not advisable for everybody. Only if you have a permanent internet connection. And before that, you have to correct the base problem.
Yes, it is, and you should know it. When people start adjusting the clock one direction and the other, the /etc/adjtime file gets "confused" with wrong data. It is typically responsible for the clock jumping hours forward or backwards on every single boot. This has been known for ages, and the proper advice is to delete that file after manually adjusting the clock - and then add ntp services if you like. If you don't believe me, just read the clock threads going back for a decade, and find out how many people had their clock problem solved by just deleting that file - which is then recreated correctly by the suse clock scripts. Using NTP is just the same as setting the clock manually, but instead, automatically. Every time you move the clock, the adjtime file is adjusted too, recording how fast or slow the system clock is compared to the CMOS clock. Jump it one hour, and the file will record that, and repeat it on boot. That's the problem, and it is known. - -- Cheers / Saludos, Carlos E. R. (from 11.2 x86_64 "Emerald" GM (Elessar)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAkx8/HgACgkQU92UU+smfQW8fACcCDaNTyWqCIBus7ZCOMi/+v+Y pLkAoIw+7Mz1GcVSeHWZqVUoniBNdDjr =H+ao -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 08/29/2010 07:55 PM, Carlos E. R. wrote:
Time issued solved, as it turns out I had everything setup correctly, was a bug of some sort. Just today I applied an update/patch for 2 packages yast2-country, yast2-country-data. The patch for yast2-country talked about the problem I was having, or I was having it's working great now. This was a bug somewhere apparently, thanks for all the good suggestions. Tony -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2010-09-09 02:11, Tony wrote:
On 08/29/2010 07:55 PM, Carlos E. R. wrote:
Curious! I had no idea about that, of course. Thanks for telling us. - -- Cheers / Saludos, Carlos E. R. (from 11.2 x86_64 "Emerald" GM (Elessar)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAkyKygIACgkQU92UU+smfQUYbQCgkU0OH85sq6Qe4NU4JU0hgp6o mmMAniQ6DoTplU2exwjjZ7h6CTG2HrDw =TQJG -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Tony wrote:
I'm open to ideas. NTP.
Configure the computer to use an NTP server, to get the correct time. Linux always runs NTP at boot and periodically afterwards. You can also set Windows to use NTP and also to not change the time for standard/daylight savings times. IIRC, Windows sets the hardware clock on time change, whereas Linux changes the offset and leaves the hardware clock alone. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 2010-08-29 22:19, Tony wrote:
It does not matter how you set it up, local or utc. Linux can handle both. However, after you change the settings (in YaST) and set up the clock, you have to delete the "/etc/adjtime" file (it will be recreated). To avoid problems with how the desktop might handle the clock, manipulate it on an xterm, as root ("su -", the dash is important), with the command "date". -- Cheers / Saludos, Carlos E. R. (from 11.2 x86_64 "Emerald" GM (Elessar))
On Mon, Aug 30, 2010 at 02:55:04AM +0200, Carlos E. R. wrote:
This suggestion is misleading and not needed. Please follow the advice given by James in this thread. That's the correct way to address your issue. Lars -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2010-08-31 13:09, Lars Müller wrote:
This suggestion is proper and proven.
Please follow the advice given by James in this thread. That's the correct way to address your issue.
Please follow my advice. Please be polite and prove your point. You are as Suse employee and should know better than blatantly disregard advices like that. :-/ - -- Cheers / Saludos, Carlos E. R. (from 11.2 x86_64 "Emerald" GM (Elessar)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAkx853UACgkQU92UU+smfQUAwACgg97P6QFekOv9JCaZf77gopU5 frkAniYTFv3fbomHIN4aolCm3ynMy+Mm =4Ru5 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tue, Aug 31, 2010 at 01:28:53PM +0200, Carlos E. R. wrote:
It is not as this might lead to non continous time changes. That's why running ntpd on a host all the time compared to calling ntpdate called by cron is of advantage.
Hey, your advice is not the correct way to address time issues. That's it. There is nothing to add as James already gave the correct instructions. EOT Lars -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2010-08-31 13:37, Lars Müller wrote:
On Tue, Aug 31, 2010 at 01:28:53PM +0200, Carlos E. R. wrote:
Calling ntpd is not advisable for everybody. Only if you have a permanent internet connection. And before that, you have to correct the base problem.
Yes, it is, and you should know it. When people start adjusting the clock one direction and the other, the /etc/adjtime file gets "confused" with wrong data. It is typically responsible for the clock jumping hours forward or backwards on every single boot. This has been known for ages, and the proper advice is to delete that file after manually adjusting the clock - and then add ntp services if you like. If you don't believe me, just read the clock threads going back for a decade, and find out how many people had their clock problem solved by just deleting that file - which is then recreated correctly by the suse clock scripts. Using NTP is just the same as setting the clock manually, but instead, automatically. Every time you move the clock, the adjtime file is adjusted too, recording how fast or slow the system clock is compared to the CMOS clock. Jump it one hour, and the file will record that, and repeat it on boot. That's the problem, and it is known. - -- Cheers / Saludos, Carlos E. R. (from 11.2 x86_64 "Emerald" GM (Elessar)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAkx8/HgACgkQU92UU+smfQW8fACcCDaNTyWqCIBus7ZCOMi/+v+Y pLkAoIw+7Mz1GcVSeHWZqVUoniBNdDjr =H+ao -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (5)
-
Carlos E. R. -
Carlos E. R. -
James Knott -
Lars Müller -
Tony