You need to start by editing the /etc/inet/ntp.conf file
# cat /etc/inet/ntp.conf
# define driftfile
driftfile /etc/inet/ntp.drift# define servers:
server pool.ntp.org
server pool.ntp.org# define peers:
peer ntpb.server.comany.com
peer ntpc.server.comany.com
Now you need to start up the ntp deamon.
Below is how you would do it in soalris 10.
root@server#svcadm enable ntp
root@server#svcs |grep ntp
online 13:35:01 svc:/network/ntp:default<p> [root@server# ps -ef|grep ntp<br /> root 1459 1188 0 13:37:23 console 0:00 grep ntp<br /> root 1393 1 0 13:35:01 ? 0:00 /usr/lib/inet/xntpd </p>
You can also check the status using ntpq command at the command line. There are many other useful commands that can be used for ntpq, which you can see by issuing the command help.
ntpq> peers
remote refid st t when poll reach delay offset jitter
==============================================================================
+64.247.17.248 99.150.184.201 2 u 597 1024 377 28.365 11.667 26.918
-ns1.keeleysam.c 99.150.184.201 2 u 579 1024 377 66.606 29.525 105.990
+server1-a.your. 64.202.112.75 2 u 98 1024 377 45.574 -4.273 1.323
*time.nist.gov .ACTS. 1 u 316 1024 157 71.618 -3.789 0.983
ntpq>
Other wise use the approate /etc/init.d/ntpd script
Some important notes to keep in mind when setting up ntp.
If the accuracy of a clock becomes too insufficient (off by more than about 17 minutes), NTP aborts the NTP daemon, with the assumption that something has gone wrong with either the client or server. In order to synchronize well with a server, the client needs to avoid step adjustments.1
Which means if you clock is more then 17 minutes off when settign up NTP you should set it by hand first because NTP gets angry if it is off by more then 17 seconds