486 travels ahead in time!

[Joe Foster]

In article <91326 at mbf.UUCP> janine at mbf.UUCP (Janine Rivas) writes:

>I have a client who is running Xenix 2.3.2 on an Acer 1200, which is a
>486 system.  The system time gains several days per real day.  I think
>that the problem is a program called /etc/setclock, which is reported
>missing each time he reboots.  If I pull this file off of the install
>floppies, will this fix it?

Try doing a "cat /dev/clock" and comparing its output with that of "date".
"/dev/clock" is the interface to the hardware real-time clock, while "date"
will report the kernel's idea of the time. If they're different, then XENIX's
idea of how many interrupts the system timer generates per second is likely
to be screwed up. On most machines, clock ticks occur every 0.02 second. I
can't seem to find a kernel tunable parameter for this, however. There is
a shell variable named HZ, defined in the rc files, /.profile, and
/etc/default/login. This is described in the Administrator's guide, page
19-15. I don't know if this will solve your problem, but it's worth a try.
Your client could also have a device installed which is generating interrupts
on the same line as the clock, causing the kernel to think more time has
elapsed than it should.

>janine
>-- 
>...!uunet!ccicpg!mbf!janine

Joe Foster
6600joef at ucsbuxa.ucsb.edu

>MAI Systems has NO idea what I do!  And they have nothing to do with the
>questions I post.  #include <rest_of_std_disclaimer>

*I* have no idea what I do! ;-)