If I want to get my server to periodically check against a time server, is it just a question of adding ntpd into cronjob or is there more to it (parameters, gotchas, etc?) Thanks John
John wrote:
If I want to get my server to periodically check against a time server, is it just a question of adding ntpd into cronjob or is there more to it (parameters, gotchas, etc?)
It's a lot easier than that. Just configure NTP in Yast to point to your favourite time server and save the settings. There is nothing more to do. NTP will determine how often it has to phone home.
James Knott wrote:
John wrote:
If I want to get my server to periodically check against a time server, is it just a question of adding ntpd into cronjob or is there more to it (parameters, gotchas, etc?)
It's a lot easier than that. Just configure NTP in Yast to point to your favourite time server and save the settings. There is nothing more to do. NTP will determine how often it has to phone home.
Thanks, James. I'd hoped that it would be simple and half thought there might already be some automation of the process! I'll just let YaST get on with the job J
On Sunday 01 October 2006 18:38, John wrote:
James Knott wrote:
John wrote:
If I want to get my server to periodically check against a time server, is it just a question of adding ntpd into cronjob or is there more to it (parameters, gotchas, etc?)
It's a lot easier than that. Just configure NTP in Yast to point to your favourite time server and save the settings. There is nothing more to do. NTP will determine how often it has to phone home.
Thanks, James. I'd hoped that it would be simple and half thought there might already be some automation of the process!
I'll just let YaST get on with the job
A potential 'gotcha': You can't test your remote time server with the ntp client configuration module in YaST when the firewall is running. This is because the service hasn't been enabled yet and the port is still closed by the firewall. 'Stop' the firewall using 'expert mode' in YaST's runlevel editor. The lower-left control lets you 'stop' and 'start' processes at will, as opposed to the enable/disable controls on the lower-right. Keep the runlevel editor window open after you've dropped the firewall and launch YaST's ntp client configuration module. Test your remote ntp server and enable the ntp client configuration, which will open the appropriate port in the firewall. Bring the firewall back up and close the runlevel editor. hth & regards, Carl
* Carl Hartung <suselinux@cehartung.com> [10-01-06 19:35]:
A potential 'gotcha': You can't test your remote time server with the ntp client configuration module in YaST when the firewall is running. This is because the service hasn't been enabled yet and the port is still closed by the firewall.
IIRC, I didn't have any problem with yast in 10.1. I was able to check the connection and got a successful answer from yast w/o dropping the firewall. The yast script must alter the firewall temporarily during ntp setup. (again, IIRC :^) ). -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/gallery2
On Sunday 01 October 2006 22:59, Patrick Shanahan wrote:
* Carl Hartung <suselinux@cehartung.com> [10-01-06 19:35]:
A potential 'gotcha': You can't test your remote time server with the ntp client configuration module in YaST when the firewall is running. This is because the service hasn't been enabled yet and the port is still closed by the firewall.
IIRC, I didn't have any problem with yast in 10.1. I was able to check the connection and got a successful answer from yast w/o dropping the firewall. The yast script must alter the firewall temporarily during ntp setup. (again, IIRC :^) ).
Hi Patrick, It's been so long since I configured it here I can't remember. ;-) I *do* know I've had to drop the firewall in versions up to 10.0 for it to 'see' and test the server, but it wouldn't surprise me if it's been fixed since. Carl
On Monday 02 October 2006 00:28, James Knott wrote:
John wrote:
If I want to get my server to periodically check against a time server, is it just a question of adding ntpd into cronjob or is there more to it (parameters, gotchas, etc?)
It's a lot easier than that. Just configure NTP in Yast to point to your favourite time server and save the settings. There is nothing more to do. NTP will determine how often it has to phone home.
After configuring this in Yast, is there a way to see if NTP really checks and corrects the time and when and how much? Daniel -- Daniel Bauer photographer Basel Switzerland professional photography: http://www.daniel-bauer.com Madagascar special: http://www.sanic.ch
On Monday 02 October 2006 00:12, Daniel Bauer wrote:
On Monday 02 October 2006 00:28, James Knott wrote:
John wrote:
If I want to get my server to periodically check against a time server, is it just a question of adding ntpd into cronjob or is there more to it (parameters, gotchas, etc?)
It's a lot easier than that. Just configure NTP in Yast to point to your favourite time server and save the settings. There is nothing more to do. NTP will determine how often it has to phone home.
After configuring this in Yast, is there a way to see if NTP really checks and corrects the time and when and how much?
Yeah, but don't rush off to do it. Time sync takes a few minutes the first time but then it will keep it spot on. As root: xntpdc That will give you a ntpdc> prompt. They type peers and you get something like this: ntpdc> peers remote local st poll reach delay offset disp ======================================================================= =LOCAL(0) 127.0.0.1 10 64 377 0.00000 0.000000 0.03088 *bigben.cac.wash 206.174.72.90 1 1024 177 0.04111 -0.015224 0.27734 If you list more than one time server in Yast (Its a good idea to do so) then the one with the asterisk is the one you are synked to. You exit xntpdc with exit. help for help. man for man ;-) -- _____________________________________ John Andersen
On Monday 02 October 2006 10:18, John Andersen wrote:
On Monday 02 October 2006 00:12, Daniel Bauer wrote:
On Monday 02 October 2006 00:28, James Knott wrote:
John wrote:
If I want to get my server to periodically check against a time server, is it just a question of adding ntpd into cronjob or is there more to it (parameters, gotchas, etc?)
It's a lot easier than that. Just configure NTP in Yast to point to your favourite time server and save the settings. There is nothing more to do. NTP will determine how often it has to phone home.
After configuring this in Yast, is there a way to see if NTP really checks and corrects the time and when and how much?
Yeah, but don't rush off to do it. Time sync takes a few minutes the first time but then it will keep it spot on.
As root:
xntpdc
That will give you a ntpdc> prompt. They type peers
and you get something like this: ntpdc> peers remote local st poll reach delay offset disp ======================================================================= =LOCAL(0) 127.0.0.1 10 64 377 0.00000 0.000000 0.03088 *bigben.cac.wash 206.174.72.90 1 1024 177 0.04111 -0.015224 0.27734
If you list more than one time server in Yast (Its a good idea to do so) then the one with the asterisk is the one you are synked to.
You exit xntpdc with exit. help for help. man for man ;-)
thanks! Daniel -- Daniel Bauer photographer Basel Switzerland professional photography: http://www.daniel-bauer.com Madagascar special: http://www.sanic.ch
participants (6)
-
Carl Hartung -
Daniel Bauer -
James Knott -
John -
John Andersen -
Patrick Shanahan