On Tue, Aug 31, 2010 at 01:28:53PM +0200, Carlos E. R. wrote:
On 2010-08-31 13:09, Lars Müller wrote:
On Mon, Aug 30, 2010 at 02:55:04AM +0200, Carlos E. R. wrote:
On 2010-08-29 22:19, Tony wrote:
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.
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".
This suggestion is misleading and not needed.
This suggestion is proper and proven.
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.
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. :-/
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