Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

16
  • 2
    I don't really know. :-) I had trouble once trying to run service from rc.local and cron but I managed to fix it using /etc/init.d/xxx instead. Actually I think you don't have to give the full path to ntpdate, I like to use full paths in scripts just to be sure the right file wiill be found. Commented Feb 14, 2013 at 21:43
  • 2
    OK, this was apparently the problem. Now the clock is being updated as soon as the network connection is established. Thanks. Commented Feb 16, 2013 at 1:23
  • 4
    I did found out that the us.pool.ntp.org is more responsive. Commented Feb 16, 2013 at 1:25
  • 11
    With the -u option, you don't need to stop the ntp service: sudo ntpdate -u time.nist.gov Commented Mar 3, 2017 at 14:09
  • 1
    ntp is deprecated in newer versions. Instead use systemd-timesyncd.service. Commented Aug 18, 2019 at 11:46