Mailinglist Archive: opensuse (3139 mails)
| < Previous | Next > |
Re: [SLE] quick question about checking time
- From: Carl Hartung <suselinux@xxxxxxxxxxxxx>
- Date: Sun, 1 Oct 2006 23:33:07 +0000 (UTC)
- Message-id: <200610011932.51033.suselinux@xxxxxxxxxxxxx>
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
> 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
| < Previous | Next > |