10 More Discussions You Might Find Interesting
1. 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
2. Red Hat
I wanted to know which should be the best way to sync time for a linux machine. We have an application server and a database server, both using RHEL 5.8 as the OS. It is important that the time on both these servers match together and also sync with a common time source. As per my knowledge, these... (11 Replies)
Discussion started by: RHCE
11 Replies
3. UNIX for Dummies Questions & Answers
I have a VirtualBox w2008r2 Domain Controller running on a Solaris 10 server. I have the time on the Virtual machine set to Default time sync (bios clock) and the Solaris server set to sync to
0 8,20 * * * /usr/sbin/ntpdate tick.usno.navy.mil tock.usno.navy.mil >> /tmp/ntp.log
My problem is... (2 Replies)
Discussion started by: SIFT3R
2 Replies
4. 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
5. Solaris
I have 2 sol 10 OS boxes in replication and there is a 6 minutes time difference in GMT zone. How I can sync? they are not on public network. (2 Replies)
Discussion started by: chandravadrevu
2 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 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
8. 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
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) System Manager's Manual ntpdate(8)
NAME
ntpdate - set the date and time via NTP (Network Time Protocol)
SYNOPSIS
/usr/sbin/ntpdate [-bdqsuv] [-a key#] [-e authdelay] [-k keyfile] [-o version] [-p samples] [-t timeout] server1 server2 server3...
OPTIONS
Tells ntpdate to step the system time immediately to match NTP. Use this option only when booting the system. Prints configuration and
debugging information. Queries the server(s) and prints the information received; the date and time are not set. Tells ntpdate to log its
actions through the syslog(3) facility rather than to the standard output. This is useful when running the program from cron(8). Tells
ntpdate to use an unprivileged port to send the packets from. This is useful when you are 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 unprivileged ports. Runs
in verbose mode. Specifies that all packets should be authenticated using the key number provided. Specifies an authentication processing
delay, in seconds (see xntpd(8) for details). This number is usually small enough to be negligible for ntpdate's purposes, though specify-
ing a value may improve timekeeping on very slow CPU's. Specifies that authentication keys will be read from keyfile instead of the
default /etc/ntp.keys file. This file should be in the format described in xntpd(8). Forces ntpdate to poll as a version implementation.
By default ntpdate claims to be an NTP version 3 implementation in its outgoing packets. Some older software will decline to respond to
version 3 queries. Acquires a specified number of samples from each server. The range of values for samples is from 1 and 8, inclusive.
The default is 4. Waits timeout seconds for a response. Any value entered will be rounded to a multiple of 0.2 seconds. The default is 1
second, a value suitable for polling across a LAN.
DESCRIPTION
The ntpdate command sets the local date and time by polling the Network Time Protocol server(s) on the host(s) given as 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
the standard NTP clock filter and selection algorithms are applied to select the best of these. The ntpdate command is run from
/sbin/init.d/settime to set the time of day at boot time, if NTP is configured. (See ntpsetup(8) for information on configuring NTP.) Note
that ntpdate's reliability and precision will improve dramatically with greater numbers of servers. While a single server may be used,
better performance and integrity will be obtained by providing at least three or four servers, if not more.
Time adjustments are made by ntpdate in one of the following ways: If ntpdate determines your clock is off by more than 0.5 seconds, it
steps the time by calling settimeofday(2). If the error is less than 0.5 seconds, however, it will by default slew the clock's time by a
call to adjtime(2) with the offset.
The latter technique is less disruptive and more accurate when the offset is small, and works quite well when ntpdate is run by cron every
hour or two. The adjustment made in the latter case is actually 50% larger than the measured offset since this will tend to keep a badly
drifting clock more accurate (at some expense to stability, though this tradeoff is usually advantageous).
Ntpdate will decline to set the date if an NTP server daemon (for example, xntpd(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 timekeep-
ing to avoid stepping the clock.
Note
Because of significant changes in NTP version 3, you should check all scripts that use the ntpdate command for correct usage and output.
ERRORS
A common problem is polling a server using the wrong query version number or wrong authentication key. If either occurs, ntpdate prints
the following error message: 18 Apr 10:20:28 ntpdate(1192]: no server
suitable for synchronization found
At boot time, if NTP is not configured, the ntpdate prints the following message: WARNING: ntpdate cannot succeed, please check your
NTP configuration
EXAMPLES
The following command line sets the date and time after polling server host1.dec.com as a version 2 implementation: /usr/sbin/ntpdate -o 2
host1.dec.com The following command line sets the date and time after polling server host2.dec.com. All packets are authenticated using
authentication key 1. /usr/sbin/ntpdate -a 1 host2.dec.com
FILES
Specifies the command path Contains the encryption keys used by ntpdate
SEE ALSO
Commands: ntpq(8), xntpd(8), xntpdc(8)
Files: ntp.conf(4)
ntpdate(8)
