10 More Discussions You Might Find Interesting
1. Red Hat
Hi,
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?
# ntpq -p
... (3 Replies)
Discussion started by: pjeedu2247
3 Replies
2. Linux
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)
Discussion started by: kimurayuki
2 Replies
3. Fedora
hi guys
I have several Red Hat 5.7(7) all of them sync time with two NTP Servers based on Windows but the issue is I configure the NTP service, I start the ntp service and use ntpdate -u to set the time the first time
This is what I do
1. Configure /etc/ntp.conf
restrict default kod... (2 Replies)
Discussion started by: karlochacon
2 Replies
4. Linux
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)
Discussion started by: MichaelLi
1 Replies
5. Red Hat
Hi Expert,
One on my server keep logging this error below, how to fix this issue?
Thank you.
Reggy.
pluton02:/home/reggy --> sudo grep "ntpd" /var/log/messages | tail
Oct 6 00:26:18 pluton02 ntpd: time reset -6.588403 s
Oct 6 00:26:18 pluton02 ntpd: frequency error -512 PPM exceeds... (0 Replies)
Discussion started by: regmaster
0 Replies
6. Solaris
Ok, I have 4 production systems. There is one NTP server for all four systems. In each system there is one Solaris 10 box that points to that NTP server. All of the other machines in the system point to the Solaris 10 machine to get their time sync.
All four Solaris 10 machines have essentially... (2 Replies)
Discussion started by: DeCoTwc
2 Replies
7. UNIX for Advanced & Expert Users
Hello, colleges!
I need to synchronize time on several thousands device (UTM-1 Edge Appliances - All inclusive, all secure, all branch offices.) which don`t understand summer time at all. But in my country summer time are used.
I plan to sync it with NTP server with modificated time: plus one... (2 Replies)
Discussion started by: chmelvv
2 Replies
8. UNIX for Advanced & Expert Users
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)
Discussion started by: Sunguy222
2 Replies
9. UNIX for Advanced & Expert Users
can anybody tel lme,how to instal NTS -150 on a unix network,it needs some patch to fetch time frm serve,,?? (2 Replies)
Discussion started by: pesty
2 Replies
10. UNIX for Dummies Questions & Answers
Is there a utility which offers the ability to utilize NTP to sync time on machine.
If so please point to man page or web site (3 Replies)
Discussion started by: SmartJuniorUnix
3 Replies
NTPDATE(8) BSD System Manager's Manual NTPDATE(8)
NAME
ntpdate -- set the date and time via NTP
SYNOPSIS
ntpdate [-bBdoqsuv] [-a key] [-e authdelay] [-k keyfile] [-o version] [-p samples] [-t timeout] server ...
DESCRIPTION
Note: The functionality of this program is now available in the ntpd(8) program. See the -q command line option in the ntpd(8) page. After
a suitable period of mourning, the ntpdate utility is to be retired from this distribution.
The ntpdate utility sets the local date and time by polling the Network Time Protocol (NTP) server(s) given as the server arguments to deter-
mine the correct time. It must be run as root on the local host. A number of samples are obtained from each of the servers specified and a
subset of the NTP clock filter and selection algorithms are applied to select the best of these. Note that the accuracy and reliability of
ntpdate depends on the number of servers, the number of polls each time it is run and the interval between runs.
The following options are available:
-a key Enable the authentication function and specify the key identifier to be used for authentication as the argument key. The keys and
key identifiers must match in both the client and server key files. The default is to disable the authentication function.
-B Force the time to always be slewed using the adjtime(2) system call, even if the measured offset is greater than +-128 ms. The
default is to step the time using settimeofday(2) if the offset is greater than +-128 ms. Note that, if the offset is much greater
than +-128 ms in this case, it can take a long time (hours) to slew the clock to the correct value. During this time, the host
should not be used to synchronize clients.
-b Force the time to be stepped using the settimeofday(2) system call, rather than slewed (default) using the adjtime(2) system call.
This option should be used when called from a startup file at boot time.
-d Enable the debugging mode, in which ntpdate will go through all the steps, but not adjust the local clock. Information useful for
general debugging will also be printed.
-e authdelay
Specify the processing delay to perform an authentication function as the value authdelay, in seconds and fraction (see ntpd(8) for
details). This number is usually small enough to be negligible for most purposes, though specifying a value may improve timekeeping
on very slow CPU's.
-k keyfile
Specify the path for the authentication key file as the string keyfile. The default is /etc/ntp.keys. This file should be in the
format described in ntpd(8).
-o version
Specify the NTP version for outgoint packets as the integer version, which can be 1 or 2. The default is 3. This allows ntpdate to
be used with older NTP versions.
-p samples
Specify the number of samples to be acquired from each server as the integer samples, with values from 1 to 8 inclusive. The default
is 4.
-q Query only - don't set the clock.
-s Divert logging output from the standard output (default) to the system syslog(3) facility. This is designed primarily for conve-
nience of cron(8) scripts.
-t timeout
Specify the maximum time waiting for a server response as the value timeout, in seconds and fraction. The value is rounded to a mul-
tiple of 0.2 seconds. The default is 1 second, a value suitable for polling across a LAN.
-u Direct ntpdate to use an unprivileged port for outgoing packets. This is most useful when behind a firewall that blocks incoming
traffic to privileged ports, and you want to synchronise with hosts beyond the firewall. Note that the -d option always uses unpriv-
ileged ports.
-v Be verbose. This option will cause ntpdate's version identification string to be logged.
The ntpdate utility can be run manually as necessary to set the host clock, or it can be run from the host startup script to set the clock at
boot time. This is useful in some cases to set the clock initially before starting the NTP daemon ntpd(8). It is also possible to run
ntpdate from a cron(8) script. However, it is important to note that ntpdate with contrived cron(8) scripts is no substitute for the NTP
daemon, which uses sophisticated algorithms to maximize accuracy and reliability while minimizing resource use. Finally, since ntpdate does
not discipline the host clock frequency as does ntpd(8), the accuracy using ntpdate is limited.
Time adjustments are made by ntpdate in one of two ways. If ntpdate determines the clock is in error more than 0.5 second it will simply
step the time by calling the system settimeofday(2) routine. If the error is less than 0.5 seconds, it will slew the time by calling the
system adjtime(2) routine. The latter technique is less disruptive and more accurate when the error is small, and works quite well when
ntpdate is run by cron(8) every hour or two.
The ntpdate utility will decline to set the date if an NTP server daemon (e.g., ntpd(8)) is running on the same host. When running ntpdate
on a regular basis from cron(8) as an alternative to running a daemon, doing so once every hour or two will result in precise enough time-
keeping to avoid stepping the clock. ntpd(8).
FILES
/etc/ntp.keys contains the encryption keys used by ntpdate.
SEE ALSO
ntpd(8)
BUGS
The slew adjustment is actually 50% larger than the measured offset, since this (it is argued) will tend to keep a badly drifting clock more
accurate. This is probably not a good idea and may cause a troubling hunt for some values of the kernel variables kern.clockrate.tick and
kern.clockrate.tickadj.
BSD
January 6, 2000 BSD