On Tue, 24 Jun 2014, Dale Snell wrote:

> I really doubt that running over the wireless network has anything to do
> with your problem. So...

Dale,

   After reading Larry's response I agree: it's the on-and-off nature of
laptop use that prevents ntpd from running long enough to get sync'ed and
stay there.

> 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.

   Yeah, ntpd starts when the system boots; it's in /etc/rc.d/rc.local.

> Anyway, I hope this helps.

   Probably does. Slackware-14.1 still has /usr/sbin/ntpdate; if it's been
deprecated perhaps I should just use 'ntpd -g -p' as an hourly cron job on
those portables? After all, ntpd runs on boot but after an unmeasured time
the clock creeps ahead.

Thanks,

Rich

_______________________________________________
PLUG mailing list
[email protected]
http://lists.pdxlinux.org/mailman/listinfo/plug

Reply via email to