I have two ntp servers in my cluster and I want all the nodes in my cluster to sync with either of the ntp servers or just one. Unfortunately it keep rotating the sync, between my ntp server 1, ntp server 2 and local. Is there anyway I can change the sync to avoid local?
Thank you.
Last edited by Scrutinizer; 02-25-2015 at 03:24 PM..
Reason: icode tags -> code tags
All,
How do you set a Solaris 9 server which received ntp updates from a ntp server to broadcast them on a local subnet. I have created a /etc/inet/ntp.conf file to receive the updates from a server on network and need to make this server become like a ntp relay from the main server.
Any... (1 Reply)
Hi folks,
The server time is no tgetiing synched up with the NTP server.
I tried ntpdate -u <ipadress> this is not working. please help out.
regards,
Sag. (7 Replies)
Hello all,
What would be the most convienint and proper way on syncing up the time and date on Solaris 8 servers with an NTP server?
Any help would be appreciated. Thanks (2 Replies)
All,
I need to write a script which can determine if my NTP client is X second off from the NTPD server time. I am looking for a crafty oneliner to calculate the time difference? (3 Replies)
I need to configure an NTP daemon on a "bridge-PC" connected on 2 LANs. It is expected to read the correct time on a time server on the first LAN and behave as a server for the second LAN.
Can I do both the things with ntpd?
In other words, is ntpd able to work as client and server at the same... (3 Replies)
All here, thank you for listening. Now I've set up a Linux NTP server by adding a external windows NTP server in /etc/ntp.conf. Then I start the ntpd daemon. But how often does the Linux NTP server update its time with the external NTP server? I've looked up everywhere but found no information... (1 Reply)
Hi
I am looking to have an NTP server that will support both ipv4 and ipv6 clients. Is there anything specific about the configuration that I should be looking at? (7 Replies)
Hi folks, I have developed a Linux server for my customer. After migrating the server to my customer site, I was trying to sync its time to the NTP time servers at my customer site.
Below is the ntp.conf:
% vi /etc/ntp.conf
# Permit time synchronization with our time source, but do not
# permit... (2 Replies)
We had a network problem a couple of days before that caused 1 interface to down and up. But today I have noticed that our date is wrong, our system have 4 servers and the other 3 are OK.
I used <date> command, the result is: Fri Jan 2 17:57:55 ICT 1970
I have tried set date to be the same as... (3 Replies)
Discussion started by: salvation3103
3 Replies
LEARN ABOUT DEBIAN
ntpd.conf
NTPD.CONF(5) File Formats Manual NTPD.CONF(5)NAME
ntpd.conf - Network Time Protocol daemon configuration file
DESCRIPTION
This manual page describes the format of the ntpd(8) configuration file.
The optional weight keyword permits finer control over the relative importance of time sources (servers or sensor devices). Weights are
specified in the range 1 to 10; if no weight is given, the default is 1. A server with a weight of 5, for example, will have five times
more influence on time offset calculation than a server with a weight of 1.
ntpd.conf has the following format:
Empty lines and lines beginning with the `#' character are ignored.
Keywords may be specified multiple times within the configuration file. They are as follows:
listen on address
OpenNTPd has the ability to sync the local clock to remote NTP servers and, if this directive is specified, can act as NTP server
itself, redistributing the local clock.
Specify a local IP address or a hostname the ntpd(8) daemon should listen on to enable remote clients synchronization. If it
appears multiple times, ntpd(8) will listen on each given address. If `*' is given as an address, ntpd(8) will listen on all local
addresses. ntpd(8) does not listen on any address by default. For example:
listen on *
or
listen on 127.0.0.1
listen on ::1
sensor device [correction microseconds] [weight weight-value]
Specify a timedelta sensor device ntpd(8) should use. The sensor can be specified multiple times: ntpd(8) will use each given sen-
sor that actually exists. Non-existent sensors are ignored. If `*' is given as device name, ntpd(8) will use all timedelta sensors
it finds. ntpd(8) does not use any timedelta sensor by default. For example:
sensor *
sensor udcf0
An optional correction in microseconds can be given to compensate for the sensor's offset. The maximum correction is 127 seconds.
For example, if a DCF77 receiver is lagging 15ms behind actual time:
sensor udcf0 correction 15000
server address [weight weight-value]
Specify the IP address or the hostname of an NTP server to synchronize to. If it appears multiple times, ntpd(8) will try to syn-
chronize to all of the servers specified. If a hostname resolves to multiple IPv4 and/or IPv6 addresses, ntpd(8) uses the first
address. If it does not get a reply, ntpd(8) retries with the next address and continues to do so until a working address is found.
For example:
server 10.0.0.2 weight 5
server ntp.example.org weight 1
To provide redundancy, it is good practice to configure multiple servers. In general, best accuracy is obtained by using servers
that have a low network latency.
servers address [weight weight-value]
As with server, specify the IP address or hostname of an NTP server to synchronize to. If it appears multiple times, ntpd(8) will
try to synchronize to all of the servers specified. Should the hostname resolve to multiple IP addresses, ntpd(8) will try to syn-
chronize to all of them. For example:
servers pool.ntp.org
FILES
/etc/openntpd/ntpd.conf
default ntpd(8) configuration file
SEE ALSO ntpd(8), sysctl(8)HISTORY
The ntpd.conf file format first appeared in OpenBSD 3.6 .
$Mdocdate: October 2 2007 $ NTPD.CONF(5)