On Wed, Dec 15, 1999 at 11:12:10PM +0100, Gustav Schaffter wrote:
> Hi,
>
> I had lots of problems with my clocks. Then I started to execute:
>
> #hwclock --set --date="`rdate -p ben.cs.wisc.edu | cut -f 2`" --utc
> #rdate -s ben.cs.wisc.edu
>
> from my ip-up.local whenever I did dial-up. After about a week, my
> hardware clock was stable. Now I rarely see any clock drift at all. I
> believe that the adjtime is executed somewhere under rc.d (haven't
> checked!) and that it's now slowly stabilizing.
>
In rc.sysinit on RH6.0 only, there is a line '$CLOCK --adjust' that
'adjusts' clock on reboot based on adjtime. If the clock has gotten
way out of whack at some point, then every reboot will mess the clock
up when it is 'adjusted' here.
> "J. Scott Kasten" wrote:
> >
> > Well, there's a couple things here to keep in mind. First, when you
> > set the system time, all you're doing is setting the SOFTWARE clock,
> > which of course gets it's time initially from the hardware on boot.
> > You can set the hardware clock from the SOFTWARE clock. "man hwclock"
> > However, there are known timezone issues, and you may or may not have
> > the system configured to have the hardware clock set to GMT.
> >
> > I for example, use the hw clock set to GMT, and the software clock
> > uses my timezone offset to display the real time. However, if I use
> > the hwclock routine to try and set the hw clock, it forgets to apply
> > the offset and sets it wrong. It seems the right way to set the
> > hw clock is to actually go through BIOS when you do a reboot. That
> > will guarantee that you avoid these zone issues and the known bugs.
> > Thus I just take the real time, account for daylight savings, and
> > apply my zone offset to get the GMT time to plug into the hw clock
> > when I boot to BIOS setup. Then when I boot Linux, everything is
> > correct.
> >
> > On Tue, Dec 14, 1999 at 10:44:56PM -0700, [EMAIL PROTECTED] wrote:
> > >
> > > Can someone help me figure out how to set the friggin' clock on my
> > > system? I'm running Red Hat 6.1. I've tried timeconfig, timetool,
> > > clock, and date, and while each of these will set my system clock when
> > > I execute them, the time will not survive a reboot. My system clock
> > > is off by about 17 hours or so. Is there a problem with the time zone
> > > setting or something? This is getting very frustrating! :(
> > >
> > > Thanks in advance!
> > >
> > > Aaron
> > >
> > >
> > > --
> > > To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
> > > as the Subject.
> > >
> >
> > --
> > J. Scott Kasten
> >
> > jsk AT tetracon-eng DOT net
> >
> > "That wasn't an attack. It was preemptive retaliation!"
> >
> > --
> > To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
> > as the Subject.
>
> --
> pgp = Pretty Good Privacy.
>
> To get my public pgp key, send an e-mail to: [EMAIL PROTECTED]
>
> Visit my web site at http://www.schaffter.com
>
>
> --
> To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
> as the Subject.
>
--
Hal B
[EMAIL PROTECTED]
--
Linux helps those who help themselves
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
