USE flags for net-misc/ntp Network Time Protocol suite/programs
||Allow ntp to be installed alongside openntpd||local|
||Add support for PARSE clocks||local|
||Enable support for libreadline, a GNU line-editing library that almost everyone wants||global|
||Provide support for Samba's signing daemon (needed for Active Directory domain controllers)||local|
Install the suite of NTP programs:
emerge --ask net-misc/ntp
To adjust ntp-client's command and upstream servers, edit the ntp-client configuration file. The default configuration is populated with:
NTPCLIENT_CMD="ntpdate" NTPCLIENT_OPTS="-s -b -u \ 0.gentoo.pool.ntp.org 1.gentoo.pool.ntp.org \ 2.gentoo.pool.ntp.org 3.gentoo.pool.ntp.org"
In /etc/ntp.conf the servers that will be used to synchronize the local time for ntpd can be specified. The default configuration is populated with:
server 0.gentoo.pool.ntp.org server 1.gentoo.pool.ntp.org server 2.gentoo.pool.ntp.org server 3.gentoo.pool.ntp.org
Time zones and location of the server do not matter for NTP; it synchronizes via UTC.
By default the Gentoo servers are listed and enabled. A list of available servers can be found on ntp.org. A home or company server here can be used, if ntpd is running and the machine is allowed access.
On systems where a network connection is not always available at boot (laptops, etc.), it might help to add the following lines to server configuration:
server 127.127.1.0 fudge 127.127.1.0 stratum 10
This sets localhost as a server with low priority, so that the daemon starts properly even without a network connection and switches to using network servers when a connection is established.
Permission are used to control who is allowed to synchronize or change permissions.
Access to NTP service allowed only from localhost.
noquery can be added to help prevent the server from being abused to conduct DDOS attacks:
# To deny other machines from changing the # configuration but allow localhost: restrict default nomodify nopeer noquery restrict 127.0.0.1
Access to NTP service allowed only from the 192.168.0.0/24 network:
# To allow machines within the local network to synchronize # their clocks with this server, but ensure they are # not allowed to configure the server or used as peers # to synchronize against, uncomment this line. # restrict 192.168.0.0 mask 255.255.255.0 nomodify nopeer notrap
Denying access to NTP's monlist functionality, used for querying traffic stats but also exploited in a denial-of-service attack.
Basic tools and common usage.
To start the ntp-client:
rc-service ntp-client start
To view the status of the client:
rc-service ntp-client status
To have the client start at boot:
rc-update add ntp-client default
This used to be the client, but its functionality is now moved into ntpd and ntp-client itself. It is purely to set the local time when started and then exits (not a service):
The server is both a client, and server. If the setup can not access net early in init, use server only instead.
If ntpd is run as a service, the time will automatically synchronize as long as the difference between the local time and the time on the server is less than 1000s (~17 mins). So it is pretty common to adjust the time initially to whatever the server time is as a trusted source:
ntpd -g -c /etc/ntp.conf
If ntpd is already running, it will not start a second time.
Add ntpd to the default runlevel to have the time synchronized automatically. There is no need to run a client when the service is running. In this case verify that ntp-client or ntpdate are not in any runlevels.
When it is confirmed the configuration is clear from ntp-client or ntpdate, add the ntpd service:
rc-service ntpd start
rc-update add ntpd default
To monitor status of the server:
rc-service ntpd status