NetNews Usenet Archive 1993 #1/NN_1993_1.iso/spool/comp/sys/sgi/18679

Internet Message Format | 1993-01-11 | 1.6 KB

Path: sparky!uunet!usc!howland.reston.ans.net!spool.mu.edu!olivea!sgigate!odin!twilight!zola!zuni!anchor!olson
From: [e-mail] (Dave Olson)
Newsgroups: comp.sys.sgi
Subject: Re: clock speed
Message-ID: <[e-mail]>
Date: 11 Jan 93 18:33:59 GMT
References: <[e-mail]>
Sender: [e-mail] (Net News)
Organization: Silicon Graphics, Inc.  Mountain View, CA
Lines: 24

In <[e-mail]> [e-mail] (Jeffrey Scott Traigle) writes:
| Something that I have noticed since beginning administrating SGIs
| several months ago is that the clock on them run fast. Within three
| to four days of setting the time on them, they are around 20 minutes
| fast. Is this something inherent in SGIs or is it just something with
| our setup?

This should not be true of any but our oldest systems.  Are you sure
that you aren't running timed, timeslave, or ntp, and the master
time server is off?

In any case, there is a kernel variable that can be set (timed puts
an appropriate value in /usr/tmp/.timetrim by default, which of course
will only be valid if the master keeps good time) to adjust the
system clock in the event that the machine is not running any kind
of time synchronization software.

See the discussion at the variable 'timetrim' in /usr/sysgen/master.d/kernel.
If you change it, run /etc/init.d/autoconfig to generate a new kernel,
and then reboot.
--
Let no one tell me that silence gives consent,  |   Dave Olson
because whoever is silent dissents.             |   Silicon Graphics, Inc.
    Maria Isabel Barreno                        |   [e-mail]