Gotta second this advice. When I do a Debian install, there's also the option
for using UTC or local time. I usually make the wrong choice, though, and my
clock is 4-5 hours behind.
To get around that, I use NTP. That way my time isn't hardware dependent at
all: it's dependent on someone else's hardware/software, somewhere else in
the world! :-) If you do a google search for it, you'll find it easily.
Although, since you've got SuSE, you've probably got it on one of the 6
million CD's that SuSE ships with.
HTH
Russell
> >
> > suse 7:55 11:55 - 4 hrs.
>
> This -4 hours id kinda suspect to me. As it almost looks like the time
> difference between here and GMT, though I think it's really -5 hours. I
> guess the -4 could be a daylight savings time thing.
>
> > The problem appears to be with hwclock. It can be set and then system
> > time set to it. Upon reboot it will knock the system clock back by
> > exactly 4 hours,
>
> I don't know know about suse, but RedHat gives you the ability to use the
> bios system clock set at local time or UTC. Since I always select the use
> local time I don't see this problem. So I'm guessing that suse is thinking
> the UTC is being used for the system clock, but I don't know why it is
> being changed.
>
> You may want to check http://www.linuxdoc.org/LDP/sag/x2466.html "The
> Linux System Administrators' Guide: Version 0.6.2" The hardware and
> software clocks
>
> This was taken from the above url:
> Unfortunately, some PC operating systems, including MS-DOS, Windows, and
> OS/2, assume the hardware
> clock shows local time. Linux can handle either, but if the hardware clock
> shows local time, then it must be modified
> when daylight savings time begins or ends (otherwise it wouldn't show local
> time).
>
> Hope this helps
> Mike M
>
>
> _________________________________________________________
> Do You Yahoo!?
> Get your free @yahoo.com address at http://mail.yahoo.com
This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 15:43:54 EDT