Mailinglist Archive: opensuse (4570 mails)

[Yogich <yogich@xxxxxxxxxx>]

On Friday 18 November 2005 13:36, Marlier, Ian wrote:
> > -----Original Message-----
> > From: Sergey Mkrtchyan [mailto:crusoe@xxxxxxxxxx]
> > Sent: Friday, November 18, 2005 1:59 PM
> > To: suse-linux-e@xxxxxxxx
> > Subject: [SLE] Timezones seems do not match
> >
> > Hi everybody,
> > I'm living in Yerevan, Armenia. Our timezone is GMT+4. When I'm
>
> setting
>
> > my hardware clock from YaST to local time it shows the correct time,
>
> but
>
> > when I want to view the time for different timezones(...and choose the
> > city I'm living in)from the clock's settings, it shows time which
> > differs from actual up to 6 hours. It's also not correct for Moscow's
> > time...
> > Is it a bug? Or have I done something wrong?
>
> If you set your hardware clock to local time, things get all mucked up
> with Linux's handling of timezones.
>
> Set your hardware clock to GMT.  That should take care of it.

There is one caveat to the above statement (which, in and of itself is totally 
true):  If you're going to set your clocks to local time, make sure your 
system clock is also set to local time.  I was testing another distro for 
someone and discovered that, unlike SuSE, when one sets the clock to UTC and 
then wants a local time zone via...
# ln -sf /usr/share/zoneinfo/<timezone> /etc/localtime 
...it mucked up the works for cron jobs.  If I had a cron job set for 0300 
(AM, that is) it would take place as many hours later as the differential 
between the clocks.  I then got the 'bright idea' to set both clocks to local 
time & let the system think that UTC was what the machine depended upon.  
After that, I had no more problems w/time zones.

Use the above idea at your own risk.  I have never tried it on SuSE.

FWIW... 
-- 
	...Yogich