10-01-2013
9 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. 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
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. 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
5. Red Hat
Hi,
My Linux VMs are running on citrix XEN.Somehow the time drift is too high (going very fast). Even if the correct time configured using date -s command, for every 1 hr it is differing almost 5 - 10 mins.
Tried configuring ntpd (local NTP server) and still it is not synchronized.
Machine... (2 Replies)
Discussion started by: uday123
2 Replies
6. 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
7. Red Hat
Hi All,
I deployed the rhel7 server in the bare metal hardware. I want to configure the rhel7 server to sync time with bios. I tired the below commands. Still it did not sync the time with bios.
Thanks,
Kalai (3 Replies)
Discussion started by: kalpeer
3 Replies
8. Shell Programming and Scripting
Hi
I have a requirement to rsync from remote to local machine via ssh and sync files that are changed in last n hours.
pgrep to check if no other sync is running
pgrep -f rsync.*/opt > /dev/null || rsync --bwlimit=10000 -avz --delete root@X.X.X.X:/var/source/ /opt/dest/ >> /home/log 2>&1... (0 Replies)
Discussion started by: robo
0 Replies
9. Solaris
Hello,
We have Windows 10 machine connected to Sparc T5440 server via serial cable.
We access the server from the Windows 10 machine using putty via serial connection. This allows us to access ILOM and Unix.
We have recently noticed that whenever we reboot the windows machine (Windows 10),... (11 Replies)
Discussion started by: jasonu
11 Replies
ntp.keys(5) File Formats ntp.keys(5)
NAME
ntp.keys - NTP symmetric key file format configuration file
SYNOPSIS
[--option-name] [--option-name value]
All arguments must be options.
DESCRIPTION
This document describes the format of an NTP symmetric key file. For a description of the use of this type of file, see the "Authentica-
tion Support" section of the ntp.conf(5) page.
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 keys numbered between 1 and 65535 may be arbi-
trarily 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 opt_IP_list
where keyno is a positive integer (between 1 and 65535), type is the message digest algorithm, key is the key itself, and opt_IP_list is an
optional comma-separated list of IPs where the keyno should be trusted. that are allowed to serve time. Each IP in opt_IP_list may con-
tain an optional /subnetbits specification which identifies the number of bits for the desired subnet of trust. If opt_IP_list is empty,
any properly-authenticated message will be accepted.
The key may be given in a format controlled by the type field. The type MD5 is always supported. If ntpd was built with the OpenSSL
library then any digest library supported by that library may be specified. However, if compliance with FIPS 140-2 is required the type
must be either SHA or SHA1.
What follows are some key types, and corresponding formats:
MD5 The key is 1 to 16 printable characters terminated by an EOL, whitespace, or a # (which is the "start of comment" character).
SHA
SHA1
RMD160 The key is a hex-encoded ASCII string of 40 characters, which is truncated as necessary.
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(1), ntpdate(1), ntpdc(1), sntp(1)
AUTHORS
The University of Delaware and Network Time Foundation
COPYRIGHT
Copyright (C) 1992-2017 The University of Delaware and Network Time Foundation all rights reserved. This program is released under the
terms of the NTP license, <http://ntp.org/license>.
BUGS
Please send bug reports to: http://bugs.ntp.org, bugs@ntp.org
NOTES
This document was derived from FreeBSD.
This manual page was AutoGen-erated from the ntp.keys option definitions.
4.2.8p13 20 Feb 2019 ntp.keys(5)