On Mon, 2008-01-14 at 09:15 +0200, Tuomo Valkonen wrote:
[...]
> ntpdate isn't run by any of the init scripts. ntpd is, but like I
Yes, that is a usual bug/problem in common distributions[0] as there is
no real guarantee that your clock is not far off.
Add your timeservers in /etc/ntp/step-tickers whereever your
distribution looks into to decide if ntpdate should run or activate the
ntpdate init.d script.
And some distributions run `ntpdate` quite late BTW ....
> already mentioned, I doubt it would correct vastly incorrect time,
> not even being able to track and correct when it advances fast.
That the reason to activate `ntpdate` unconditionally: It sets the
current time to an (somewhat) accurate value and `ntpd` handles the
rest.
Bernd
[0]: Perhaps there is some reason for this. However I don't of any and
none came ever to my mind.
--
Firmix Software GmbH http://www.firmix.at/
mobil: +43 664 4416156 fax: +43 1 7890849-55
Embedded Linux Development and Services
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
