Mailinglist Archive: opensuse (1599 mails)

< Previous Next >
Re: [opensuse] ntp and wireless
  • From: "Carlos E. R." <robin.listas@xxxxxxxxxxxxxx>
  • Date: Wed, 28 Oct 2009 21:09:37 +0100 (CET)
  • Message-id: <alpine.LSU.2.00.0910282103190.5346@xxxxxxxxxxxxxxxx>
Hash: SHA1

On Wednesday, 2009-10-28 at 15:45 -0400, James Knott wrote:

Carlos E. R. wrote:

That's what it should do. However, if there is a big initial time
difference, it will abort. If you start the ntp service after the
network is up, first it will jump-adjust the time, then it starts the
daemon to keep it.

One ntpd option is "-g" which will allow it to ignore a big time
difference. According to ps aux, that is enabled, so that big error
shouldn't be a problem, at least once.

Yes... but not quite. A few minutes difference can take hours (even days) to get corrected by that method, because what it does is speed up or slow down the clock just a trifle, so that timing operations in the running processes are not affected (noticeably). When the clock catches with the real world time, it readjusts the speed.

A possibility to fix this would be to have a script started a few
minutes after boot, to ensure ntpd is running. There are a couple of
ways that could be done.

Things like this are designed to work with the "traditional" setup, and do work. Graphical tools in linux have some catch up to do. That is, if you have a network and want some things like ntp, nfs, samba, etc, to come up and down properly, just use the traditional network setup.

- -- Cheers,
Carlos E. R.
Version: GnuPG v2.0.9 (GNU/Linux)

To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx

< Previous Next >