Re: Possible problem with periodic daily processing

2005-07-22 Thread RW
On Friday 22 July 2005 16:24, Mike Friedman wrote:
 Because of clock drift on my system, I decided to run ntpdate daily,
 instead of just at boot time.  So, what I did was create a symlink in
 /etc/periodic/daily:  600.ntpdate - /etc/rc.d/ntpdate, thus leveraging
 the existing ntpdate script that runs at boot time.  My rc.conf already has
 'ntpdate_enable=YES' and sets 'ntpdate_program' and 'ntpdate_hosts'.
 In fact, if I cd to /etc/periodic/daily and manually enter './600.ntpdate
 start', it runs fine.

 Yet, it appears that ntpdate is NOT running automatically each day as part
 of periodic daily processing.  Any ideas on why this is the case?  Is
 there a restriction about symlinks and periodic processing?

That's not the best way to do it.

Normally ntpdate corrects gross clock errors  at boot time, and then ntpd 
keeps the clock on track by continuous adjustment.  It's covered in the 
manual.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Possible problem with periodic daily processing

2005-07-22 Thread Mike Friedman

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Fri, 22 Jul 2005 at 17:44 (+0100), RW wrote:


On Friday 22 July 2005 16:24, Mike Friedman wrote:
Because of clock drift on my system, I decided to run ntpdate daily, 
instead of just at boot time.  So, what I did was create a symlink in 
/etc/periodic/daily:  600.ntpdate - /etc/rc.d/ntpdate, thus leveraging 
the existing ntpdate script that runs at boot time.  My rc.conf already 
has 'ntpdate_enable=YES' and sets 'ntpdate_program' and 
'ntpdate_hosts'. In fact, if I cd to /etc/periodic/daily and manually 
enter './600.ntpdate start', it runs fine.


Yet, it appears that ntpdate is NOT running automatically each day as 
part of periodic daily processing.  Any ideas on why this is the case? 
Is there a restriction about symlinks and periodic processing?


That's not the best way to do it.

Normally ntpdate corrects gross clock errors at boot time, and then ntpd 
keeps the clock on track by continuous adjustment.  It's covered in the 
manual.


Yes, I suppose I should run ntpd as well.  Though I'm not sure what you 
mean by 'normally', considering that 'ntpd_enable=NO' is the default set 
in /etc/defaults/rc.conf.


Anyway, I'll just enable ntpd;  that does sound like the right way to do it.

Although I'm still curious as to why periodic daily processing didn't pick 
up my symlinked ntpdate script


Thanks.

Mike

_
Mike Friedman   System and Network Security
[EMAIL PROTECTED]  2484 Shattuck Avenue
1-510-642-1410  University of California at Berkeley
http://ack.Berkeley.EDU/~mikef  http://security.berkeley.edu
_

-BEGIN PGP SIGNATURE-
Version: PGP 6.5.8

iQA/AwUBQuEls60bf1iNr4mCEQJkIQCgjhlKioFeajvUxA4ahEdQ9nrZz1IAn0gU
RIZcAGQHhk66SBs+DmCbMkLj
=13ql
-END PGP SIGNATURE-
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Possible problem with periodic daily processing

2005-07-22 Thread RW
On Friday 22 July 2005 17:58, Mike Friedman wrote:
 Yes, I suppose I should run ntpd as well.  Though I'm not sure what you
 mean by 'normally', considering that 'ntpd_enable=NO' is the default set
 in /etc/defaults/rc.conf.

I mean it's the normal solution to the problem of long-term clock inaccuracy, 
as opposed to running ntpdate repeatedly.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]