I just looked at adjtimex. This is a c call that is used to adjust the kernel clock not the hwclock. It is what ntpd uses.
On Tue, Jun 24, 2014 at 11:56 AM, Dale Snell <[email protected]> wrote: > On Tue, 24 Jun 2014 10:49:20 -0700 (PDT) > Rich Shepard <[email protected]> wrote: > > > The ethernet-connected hosts here have static IP addresses. The > > wireless access point serves dynamic IP addresses on a different > > subnet. Only two portables use the WAP and both have a time keeping > > issue: each machine gains time and can get days ahead. > > > > While many of us wish we could gain time so everything can be > > accomplished, for the computers it is not desired. One laptop, a > > Toshiba Satellite running Slackware-14.1 booted and thought it was > > Thursday, June 26th, and 5:17 pm when it was only an hour ago. I > > reset the date and time, ran 'hwclock -w' to set the hardware clock > > to the system time, and shut down. Realizing that the reason users > > cannot run alsamixer was not having their usernames in the audio > > group, I rebooted. The system gagged because the last time /dev/sda1 > > was checked was Thursday the 26th and now it is Tuesday the 24th and > > it doesn't know how to deal with back to the past. That was fixed by > > running 'e2fsck -v -y' and waiting. > > > > So, now the kernel is happy, and I need to figure out why only the > > two portables that connect to the 'Net wirelessly through the WAP > > keep gaining time. I've set up one of the laptops to use na.pool ntp > > servers but it still keeps gaining time. My Web searches and thread > > on linuxquestions.org have produced no solution for the one laptop; > > just this morning I saw the second has the same problem and realized > > the common factor is wireless connectivity. > > > > Any ideas of why only the portables connecting via the WAP keep > > gaining time would be much appreciated. Also, any diagnostics or > > tests I can run to isolate the source of the problem would be good. > > > I really doubt that running over the wireless network has anything > to do with your problem. So... > > First off, make sure you have ntpd running on your laptops. You > can use ntpdate(8) to set the time if you need to. ntpdate is > deprecated; 'ntpd -q' is the replacement. > > If your laptop's hardware clock gains too much while the laptop is > off, then you might want to look into the adjtimex(8) program. It > will let you set up a correction factor that will keep the > hardware clock within reasonable limits. You'll have to leave > your laptop running for quite a while, the longer the better. The > man page for adjtimex(8) will tell you what you need to know. > > Anyway, I hope this helps. > > --Dale > > -- > Yet creeds mean very little, Coth answered the dark god, still speaking > almost gently. The optimist proclaims that we live in the best of all > possible worlds; and the pessimist fears this is true. > -- James Branch Cabell, "The Silver Stallion" > > _______________________________________________ > PLUG mailing list > [email protected] > http://lists.pdxlinux.org/mailman/listinfo/plug > > _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
