[armedslack] An ntp hint

Niels Horn niels.horn at gmail.com
Wed Sep 2 17:06:35 UTC 2009


To run after every boot, put in in /etc/rc.d/rc.local

Also, it is better to use one of the servers from the ntp pool.
(see http://www.pool.ntp.org/ for a list of servers).
This way you won't depend on the availability of a single time server.



Niels Horn
Rio de Janeiro, RJ
Brasil
site: www.nielshorn.net
e-mail: niels.horn at gmail.com



On Wed, Sep 2, 2009 at 1:50 PM, Phil Ehrens<phil at slug.org> wrote:
> You probably don't want to run ntpd on a plug, unless you
> are using it as a time server, but you DO want the time to
> be correct, because it's a hazard to run a networked computer
> with time skew, so you should put this in /etc/cron.daily:
>
> ~~~ snip ~~~
> #!/bin/sh
> #
> # Name: ntpsynch.sh
> #
> # Purpose: Keep the clock sane!
> #
> # Comment:
> #
> #    ntpdate is called twice because it
> #    takes two calls to get it "dead-on".
> #
> /usr/sbin/ntpdate -b time.caltech.edu 2>&1 >/dev/null
> sleep 2
> /usr/sbin/ntpdate -b time.caltech.edu 2>&1 >/dev/null
> ~~ snip ~~~
>
> It should of course also be run as early as possible at
> reboot. Slackware calls rc.ntpd from rc.M, so you should
> copy this script to /etc/rc.d/rc.ntpd as well if you
> want to be sure your clock is sane at boot.
>
> Phil
>
>




More information about the ARMedslack mailing list