OBTW, I forgot to mention, one of the most common uses of ntpdate is in the root crontab file, for example:
From the shell:
Also, here is a site dedicated to helping you find a valid time server for your site:
Quote:
The pool.ntp.org project is a big virtual cluster of timeservers providing reliable easy to use NTP service for millions of clients.
The pool is being used by millions or tens of millions of systems around the world. It's the default "time server" for most of the major Linux distributions and many networked appliances (see information for vendors).
Hello,
I'm looking for assitance on setting up network time protocol on my HP-ux boxes.
I have edit the .conf file accordingly. And /etc/services. But whenever I try and start the service nothing happens at all. No error message, nothing.
I have a SCO box as a time server and I wish... (0 Replies)
Hi experts,
I've a master server which sync to ntp time server daily by using xntpd daemon. Then my client servers will use ntpdate through cron job to synchronize the time hourly. (By using ntpupdate -s -B 'master server')
My question is, now I'll need to synchronize to a oracle server which... (2 Replies)
Hi Guys,
A weird problem. I have disabled ntpd daemon on a HP server and placed
ntpdate in crontab instead and redirected the log to a file. This command
in cron synchronizes the server with a local time server every 15 minutes.
The weird part is that on 3 specific times (5:00 am, 10:00 am,... (2 Replies)
Hi there,
Hi have a group of computers + a server (all debians) connected to each other on a LAN.
For some reasons that I've not decided and that I can't change, the computers cannot connect to the net. Moreover, the server has no ntp service.
Though, I need to find a way of setting all... (4 Replies)
as advised and documented, i'm trying to use the ntpd -gq instead of ntpdate. The result is that clock not set. as below. However ntpdate is working ok and had set the clock correctly
this is the ntp.conf file:
# cat /etc/ntp.conf
logfile /var/log/ntp.log
driftfile /var/lib/ntp/drift... (6 Replies)
Hi,
Could somebody please explain me.
why is it necessary to execute the "ntpdate" command only when ntp daemon is stopped , and also the probabale solution to reduce the high offset value.
Thanks !!
Laxxi (4 Replies)
Hi all. I'm new to this forum and Linux in general. Last month I ran into a problem at work and never got around to solving it.
We have an old Linux workstation that synchs its time to a Windows XP machine running w32time. The version of ntpdate is 4.2.0.a running on Linux kernel 2.6.17.6. It... (0 Replies)
Discussion started by: rathauneek
0 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)