10-17-2011
Have to agree with you, Otheus. By the way, Red Hat will probably be switching from ntp to Chrony in some future release. Fedora 16 has switched to Chrony.
10 More Discussions You Might Find Interesting
1. 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
2. AIX
Good morning to all,
can someone advise me how to setup aix ntp server with aix & wintel clients?
Secondly, I also require to enable the service to autostart on reboot, how do I configure this?
Thirdly, how do I configure daily autosync between clients and server?
Please advice, thanks.... (0 Replies)
Discussion started by: chongkls77
0 Replies
3. SuSE
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)
Discussion started by: sag71155
7 Replies
4. UNIX for Advanced & Expert Users
I need to find out the NTP Clients which are syncing with my NTP Server in a Unix(Linux/Solaris) Machine. For eg. How many Stratum 2 Servers sync the time with my Stratum1 Server. Is there any way to track it?
edit by bakunin: moving the thread to where it belongs: the technical forums. (4 Replies)
Discussion started by: hottyspidy
4 Replies
5. 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
6. Linux
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)
Discussion started by: vada010
3 Replies
7. Red Hat
Hi,
I have 4 machines and all are NTP configured with same ntp.conf file. But 3 machines are in sync with Time server and 4th machine is not contacting & sync with the NTP server. Please see the below details.
# service ntpd stop
Stopping ntpd: ... (0 Replies)
Discussion started by: uday123
0 Replies
8. HP-UX
Hi
I wonder if its possible to setup NTP clients running HP-UX o.s. from a solaris 10 NTP server?
FR (3 Replies)
Discussion started by: fretagi
3 Replies
9. Solaris
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
10. 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
LEARN ABOUT FREEBSD
ntp.keys
NTP.KEYS(5) BSD File Formats Manual NTP.KEYS(5)
NAME
ntp.keys -- NTP daemon key file format
SYNOPSIS
/etc/ntp.keys
DESCRIPTION
Following is a description of the format of NTP key files. For a description of the use of these files, see the "Authentication Support"
section of the ntp.conf(5) page.
In the case of DES, the keys are 56 bits long with, depending on type, a parity check on each byte. In the case of MD5, the keys are 64 bits
(8 bytes). ntpd(8) reads its keys from a file specified using the -k command line option or the keys statement in the configuration file.
While key number 0 is fixed by the NTP standard (as 56 zero bits) and may not be changed, one or more of the keys numbered 1 through 15 may
be arbitrarily set in the keys file.
The key file uses the same comment conventions as the configuration file. Key entries use a fixed format of the form
keyno type key
where keyno is a positive integer, type is a single character which defines the key format, and key is the key itself.
The key may be given in one of four different formats, controlled by the type character. The four key types, and corresponding formats, are
listed following.
S The key is a 64-bit hexadecimal number in the format specified in the DES specification; that is, the high order seven bits of each octet
are used to form the 56-bit key while the low order bit of each octet is given a value such that odd parity is maintained for the octet.
Leading zeroes must be specified (i.e., the key must be exactly 16 hex digits long) and odd parity must be maintained. Hence a zero key,
in standard format, would be given as '0101010101010101'.
N The key is a 64-bit hexadecimal number in the format specified in the NTP standard. This is the same as the DES format, except the bits
in each octet have been rotated one bit right so that the parity bit is now the high order bit of the octet. Leading zeroes must be spec-
ified and odd parity must be maintained. A zero key in NTP format would be specified as '8080808080808080'.
A The key is a 1-to-8 character ASCII string. A key is formed from this by using the low order 7 bits of each ASCII character in the
string, with zeroes added on the right when necessary to form a full width 56-bit key, in the same way that encryption keys are formed
from UNIX passwords.
M The key is a 1-to-8 character ASCII string, using the MD5 authentication scheme. Note that both the keys and the authentication schemes
(DES or MD5) must be identical between a set of peers sharing the same key number.
Note that the keys used by the ntpq(8) and ntpdc(8) programs are checked against passwords requested by the programs and entered by hand, so
it is generally appropriate to specify these keys in ASCII format.
FILES
/etc/ntp.keys the default name of the configuration file
SEE ALSO
ntp.conf(5), ntpd(8), ntpdate(8), ntpdc(8)
BUGS
ntpd(8) has gotten rather fat. While not huge, it has gotten larger than might be desirable for an elevated-priority daemon running on a
workstation, particularly since many of the fancy features which consume the space were designed more with a busy primary server, rather than
a high stratum workstation, in mind.
BSD
January 13, 2000 BSD