Emanuel Strobl <[EMAIL PROTECTED]> wrote: > Am Mittwoch, 22. September 2004 23:27 schrieb Bill Moran: > > Emanuel Strobl <[EMAIL PROTECTED]> wrote: > > > Am Mittwoch, 22. September 2004 17:19 schrieb alden.pierre: > > > > /etc/rc.conf contains the following: > > > > > > > > ntpdate_enable="YES" > > > > ntpdate_flags="timex.cs.columbia.edu" > > > > xntpd_enable="YES" # Run ntpd Network Time Protocol > > > > > > > > /etc/ntpd.conf contains the following: > > > > > > ^^^^^^^^^ > > > > > > Correct me if I'm wrong but doesn't ntpd 4.1 use ntp.conf instead of > > > ntpd.conf? > > > > > > You can try -c /etc/ntpd.conf > > > > > > -Harry > > > > In addition to this minor error ... > > > > I don't believe you can reliably run both ntpdate and xntpd. Besides, > > This is working because ntpdate is invoked only once at startup, which is, in > my case, because of possible empty BIOS-Battery where the date would be wrong > for several years which causes ntpd to refuse to adjust the time. > I use generally ntpdate at startup before ntpd keeps the kernel time in sync.
Um ... did you read my whole message? Check the ntpd man page on the -g option. If you are running ntpd, you don't need ntpdate. You answer shows that you are not familiar with the ntpd program and didn't read the rest of my email. > > if you plan to run xntpd anyway, just set xntpd_flags="-g" and it will > > behave the same as ntpdate at startup, as well as running continually > > to ensure your clock stays synced. > -- Bill Moran Potential Technologies http://www.potentialtech.com _______________________________________________ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
