All
I was assuming the OP was not running NTPD and was using ntpdate to
set system time
<quote>
ntpdate can be run manually as necessary to set the host clock, or it
can be run from the host startup script to set the clock at boot time.
This is useful in some cases to set the clock initially before starting
the NTP daemon ntpd. It is also possible to run ntpdate from a cron
script. However, it is important to note that ntpdate with contrived
cron scripts is no substitute for the NTP daemon, which uses sophisti-
cated algorithms to maximize accuracy and reliability while minimizing
resource use. Finally, since ntpdate does not discipline the host clock
frequency as does ntpd, the accuracy using ntpdate is limited.
</quote>
So I don't see anything wrong with running ntpdate or rdate once a day
if you want.. Given NTPD would be better... Probably not a critical
issue??
Back in the old days.... I would wait for the noon train to go by and
then set the clocks in the house and the computer at the same.. That
was an example of a PERFECT system.
YMMV
Marvin
On 4/19/10, Randal L. Schwartz <[email protected]> wrote:
>>>>>> "Marvin" == Marvin Kosmal <[email protected]> writes:
>
> Marvin> Good One
>
> Where "Good" here is "bad". See my other post.
>
> --
> Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
> <[email protected]> <URL:http://www.stonehenge.com/merlyn/>
> Smalltalk/Perl/Unix consulting, Technical writing, Comedy, etc. etc.
> See http://methodsandmessages.vox.com/ for Smalltalk and Seaside discussion
>
> _______________________________________________
> PLUG mailing list
> [email protected]
> http://lists.pdxlinux.org/mailman/listinfo/plug
>
_______________________________________________
PLUG mailing list
[email protected]
http://lists.pdxlinux.org/mailman/listinfo/plug
