Red Hat NETSCAPE MANAGEMENT SYSTEM 6.0 - COMMAND-LINE Manuale Utente Pagina 33

  • Scaricare
  • Aggiungi ai miei manuali
  • Stampa
  • Pagina
    / 60
  • Indice
  • SEGNALIBRI
  • Valutato. / 5. Basato su recensioni clienti
Vedere la pagina 32
33
Now allow whatever hosts/networks you are going to allow to query your
server for time – for example:
# Allowed clients
restrict 10.0.0.0 mask 255.0.0.0 nomodify
restrict 172.16.0.0 mask 255.255.224.0 nomodify
restrict 192.168.0.0 mask 255.255.0.0 nomodify
restrict 207.169.53.0 mask 255.255.255.0 nomodify
Set the logfile:
#Logfile
logconfig all
logfile /var/log/ntpd
Set the driftfile. This file will hold the “drift” or time shift due to network
latency:
# Driftfile
driftfile /etc/ntp/drift
Set “Step-
Tickers”
The server in the /etc/ntp/step-tickers file will be the ones that your server will
sync with immediately when it boots up:
vim /etc/ntp/step-tickers
Now simply add the IP addresses of your upstream servers that you’re getting
time from, one on each line, such as:
198.30.92.2
128.10.252.7
130.126.24.44
That’s it. Save and close the file.
Update Your
System Clock
Run the ntpdate command against each IP address of your upstream servers 2
or 3 times each. You should see the “jitter” come way down between the first
time you run it and the last:
ntpdate 198.30.92.2
ntpdate 198.30.92.2
ntpdate 128.10.252.7
ntpdate 128.10.252.7
ntpdate 130.126.24.44
ntpdate 130.126.24.44
Start your
Service
Start your NTP daemon:
service ntpd restart
Then turn it on to run automatically:
chkconfig –level 2345 ntpd on
Now that ntp is running, to determine if it is synchronizing properly, issue the command (wait a
couple of minutes after starting the ntpd service before running this command):
ntpq –p
This command should show output similar to below:
Vedere la pagina 32
1 2 ... 28 29 30 31 32 33 34 35 36 37 38 ... 59 60

Commenti su questo manuale

Nessun commento