Re: clock running fast

From: Federico Galvez-Durand Besnard (Federico.Besnard_at_bluewin.ch)
Date: 12/30/04

  • Next message: dtalk-ml_at_prairienet.org: "Re: clock running fast"
    Date: Thu, 30 Dec 2004 20:37:03 +0100
    To: dtalk@u.washington.edu
    
    

    Set /etc/localtime to your correct timezone before doing anything in
    your machine.
    Remove /var/db/ntpd.drift before you reboot or restart your ntpd.

    This is what I use in /etc/rc.conf:
    +++
    ntpd_enable="YES" # Run ntpd Network Time Protocol (or NO).
    ntpd_program="/usr/sbin/ntpd" # path to ntpd, if you want a different one.
    ntpd_flags="-p /var/run/ntpd.pid -f /etc/ntp/drift -l /var/log/ntp.log"
    +++

    Check ntpd messages with dmesg.

    If it does not work, this is one ntp.conf (change server to
    time.u.washington.edu or whatever is closer to you) that worked well for me:

    +++++ BEGIN /etc/ntp.conf +++++++
    # NTP configuration file
    #
    # Thu Nov 11 20:06:40 GMT+1 2004

    restrict 192.168.1.0 mask 255.255.255.0 notrust nomodify notrap
    restrict 127.0.0.1

    # servers to query
    #-------------------

    server clock.tix.ch

    restrict clock.tix.ch mask 255.255.255.255 nomodify notrap
    noquery

    +++++ END /etc/ntp.conf +++++++

    Once you get synchronised with your time-server, you can consider
    changing minpoll maxpoll to polite values.

    Fico//

    David Talkington wrote:

    > -----BEGIN PGP SIGNED MESSAGE-----
    > Hash: SHA1
    >
    > Federico Galvez-Durand Besnard wrote:
    >
    >> what do you have in :
    >> /etc/ntp.conf
    >
    >
    > Only:
    >
    > server time.u.washington.edu
    > server 127.127.1.0 fudge 127.127.1.0 stratum 10
    >
    >
    > Command line:
    >
    > /usr/sbin/ntpd -c /etc/ntp.conf -p /var/run/ntpd.pid \
    > - -f /var/db/ntpd.drift
    >
    > Thank you ... -d
    >

    _______________________________________________
    freebsd-stable@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-stable
    To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"


  • Next message: dtalk-ml_at_prairienet.org: "Re: clock running fast"

    Relevant Pages

    • Re: later kernels vs ntpd
      ... On Sunday 18 September 2005 10:46, Gene Heskett wrote: ... I had to lead the missus thru a reboot ... The next day I did a 'service ntpd restart', ...
      (Linux-Kernel)
    • Re: Restarting ntpd on address change
      ... ntpd stops functioning and must be restarted. ... /etc/rc.d/ntpd restart ... Killing one of them stops the file descriptor errors. ... My interpretation of this is that an ntpd process gets started before dhclient gets a chance to configure the address and then when the address is assigned the /etc/rc.d/ntpd restart starts a second process, but somehow fails to stop the first one. ...
      (freebsd-stable)
    • Restarting ntpd on address change
      ... ntpd stops functioning and must be restarted. ... /etc/rc.d/ntpd restart ... shows that there are two ntpd processes running. ...
      (freebsd-stable)
    • Re: ntpd vs selinux
      ... It appears that the last selinux update has killed ntpd, as shown from my messages log: ... So to get a clean restart, I did a restart, and this error was logged. ... If ntpd is still not working, the problem lies elsewhere than SELinux. ...
      (Fedora)
    • Re: ntpd vs selinux
      ... It appears that the last selinux update has killed ntpd, as shown from my messages log: ... So to get a clean restart, I did a restart, and this error was logged. ... If ntpd is still not working, the problem lies elsewhere than SELinux. ...
      (Fedora)