Cool. The biggest reason I need to do one-offs is I've had issues with time drift on some of my VMs, and enabling NTP in YaST only runs a time sync on boot. While that may be fine for computers that get started up and shut down regularly, that doesn't help much for servers that run for months at a time. So to address the time drift, I just set up a cron job to manually sync it at regular intervals. Chris
"David C. Rankin" 12/06/13 11:15 PM >>> On 12/06/2013 06:07 PM, James Knott wrote: Christopher Myers wrote: In order to keep the time on my openSuSE server at home sync'd, I use the ntpdate command: /usr/sbin/ntpdate ntp.illinois.edu
ntpdate is fine for a one shot update --or-- ust start ntp at boot and forget about it.
Why not just enable NTP in Yast?
or # chkconfig ntp on Christopher, Make sure ntp.illinois.edu is a good time server. See http://support.ntp.org/bin/view/Servers/StratumTwoTimeServers If not, use http://www.pool.ntp.org/zone/us to update your ntp.conf. If you want Illinois, then you can use ntp-0.cso.uiuc.edu, ntp-1.cso.uiuc.edu or ntp-2.cso.uiuc.edu. -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org