Re: Suggested clockspeed/taiclockd invocation at boot

Quoting Paul Jarc <[email protected]>:
> /service is for things that run continuously, not just at startup.
> 
> You want to have clockspeed running continuously; create a service
> whose run script simply exec's clockspeed.  On the master, you also
> want to publish the clock; create a service whose run script simply
> execs taiclockd.
> 
> clockspeed will not do any network communication; the clients will
> have to also be configured to run taiclock and feed the result to
> clockspeed via /usr/local/clockspeed/adjust.  At boot, you might (or
> might not) want to jump the clock into sync by feeding the taiclock
> output to clockadd.
> 
> clockspeed remembers your clock skew in
> /usr/local/clockspeed/etc/atto.  However, you will still want to get
> occasional adjustments from the master for the slaves.  That's what
> taiclock and taickockd are for.

Then what might work would be to add to /etc/rc.local:

  taiclock `dnsip my.taiclockd.server` |clockadd

And have svscan monitor an appropriate run script that can launch clockspeed and
keep it running. Or is there a better method?

With clockspeed running in the background, will it periodically adjust the time,
or is this only accomplished when clockadd is executed?

-- 
Darren Spruell
www.sancho2k.net

-------------------------------------------------
This mail sent through IMP: http://horde.org/imp/