Hi everyone! I have a not-at-all-important-but-im-curious question about NTP on SuSE. 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 However, when I want to force a timesync on my SLES servers at work, trying to use that command throws complaints as if I was just about to drive off a bridge: !!!!!!!!!!!!!! WARNING !!!!!!!!!!!!!!!!!! The ntpdate program is deprecated and should not be used any more. To quote the upstream ntp developers: "The functionality ntpdate offered is now provided by the ntpd daemon itself. If you call ntpd with the command line option -q it will retrieve the current time and set it accordingly." Please check the Network Time Protocol (NTP) daemon man page and http://support.ntp.org/bin/view/Dev/DeprecatingNtpdate for further information. You can replace the ntpdate call with "rcntp ntptimeset" to achieve an inital poll of the servers specified in /etc/ntp.conf. The program /usr/sbin/sntp offers comparable functionality to ntpdate. Specifically sntp -P no -r pool.ntp.org is equivalent to ntpdate pool.ntp.org For further details please refer to the man page of sntp. But if I try to use that sntp command on an oS box, including 13.1, it doesn't know what in the world I'm trying to do: sntp: illegal option -- P sntp - standard Simple Network Time Protocol program - Ver. 4.2.6p5 USAGE: sntp [ -<flag> [<val>] | --<name>[{=| }<val>] ]... \ [ hostname-or-IP ...] My question is - if ntpdate is so depreciated that SLES11 won't even touch it, why does openSuSE still use it instead of sntp? Chris -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
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
Why not just enable NTP in Yast? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
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
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
Le 09/12/2013 15:39, Christopher Myers a écrit :
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.
certainly not. in brand new 13.1: ps ax | grep ntp 3486 ? Ss 0:01 /usr/sbin/ntpd -p /var/run/ntp/ntpd.pid -g -u ntp:ntp -c /etc/ntp.conf the *daemon* is started at boot jdd -- http://www.dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
jdd wrote:
Le 09/12/2013 15:39, Christopher Myers a écrit :
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.
certainly not. in brand new 13.1:
Agree, it's even enabled by default, no need to do anything. -- Per Jessen, Zürich (-0.9°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 12/09/2013 09:39 AM, Christopher Myers pecked at the keyboard and wrote:
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
http://en.opensuse.org/openSUSE:Mailing_list_netiquette#Use_bottom-posting_o... Please! -- Ken Schneider SuSe since Version 5.2, June 1998 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2013-12-06 23:41, Christopher Myers wrote:
Hi everyone!
I have a not-at-all-important-but-im-curious question about NTP on SuSE.
I have known that warning for years. Call instead: rcntp ntptimeset For which you have to configure /etc/ntp.conf. It is a one shot time update.
My question is - if ntpdate is so depreciated that SLES11 won't even touch it, why does openSuSE still use it instead of sntp?
Mmmm. :-? -- Cheers / Saludos, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar)
participants (7)
-
Carlos E. R. -
Christopher Myers -
David C. Rankin -
James Knott -
jdd -
Ken Schneider - openSUSE -
Per Jessen