01-03-2006
Here is my ntp conf file ...
Here is my ntp config file ...
Quote:
$ more /etc/ntp.conf
# Prohibit general access to this service.
restrict default ignore
# Permit all access over the loopback interface. This could
# be tightened as well, but to do so would effect some of
# the administrative functions.
restrict 127.0.0.1
# -- CLIENT NETWORK -------
# Permit systems on this network to synchronize with this
# time service. Do not permit those systems to modify the
# configuration of this service. Also, do not use those
# systems as peers for synchronization.
# restrict 192.168.1.0 mask 255.255.255.0 notrust nomodify notrap
# --- OUR TIMESERVERS -----
# or remove the default restrict line
# Permit time synchronization with our time source, but do not
# permit the source to query or modify the service on this system.
# restrict mytrustedtimeserverip mask 255.255.255.255 nomodify notrap noquery
# server mytrustedtimeserverip
# --- NTP MULTICASTCLIENT ---
#multicastclient # listen on default 224.0.1.1
# restrict 224.0.1.1 mask 255.255.255.255 notrust nomodify notrap
# restrict 192.168.1.0 mask 255.255.255.0 notrust nomodify notrap
# --- GENERAL CONFIGURATION ---
#
# Undisciplined Local Clock. This is a fake driver intended for backup
# and when no outside source of synchronized time is available. The
# default stratum is usually 3, but in this case we elect to use stratum
# 0. Since the server line does not have the prefer keyword, this driver
# is never used for synchronization, unless no other other
# synchronization source is available. In case the local host is
# controlled by some external source, such as an external oscillator or
# another protocol, the prefer keyword would cause the local host to
# disregard all other synchronization sources, unless the kernel
# modifications are in use and declare an unsynchronized condition.
#
server 127.127.1.0 # local clock
fudge 127.127.1.0 stratum 10
#
# Drift file. Put this in a directory which the daemon can write to.
# No symbolic links allowed, either, since the daemon updates the file
# by creating a temporary in the same directory and then rename()'ing
# it to the file.
#
driftfile /etc/ntp/drift
broadcastdelay 0.008
#
# Authentication delay. If you use, or plan to use someday, the
# authentication facility you should make the programs in the auth_stuff
# directory and figure out what this number should be on your machine.
#
authenticate yes
#
# Keys file. If you want to diddle your server at run time, make a
# keys file (mode 600 for sure) and define the key number to be
# used for making requests.
#
# PLEASE DO NOT USE THE DEFAULT VALUES HERE. Pick your own, or remote
# systems might be able to reset your clock at will. Note also that
# ntpd is started with a -A flag, disabling authentication, that
# will have to be removed as well.
#
keys /etc/ntp/keys
server 132.249.20.60 # billthecat.sdsc.edu
server 204.152.184.72 # clock.isc.org
Please have a look ...
5 More Discussions You Might Find Interesting
1. HP-UX
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)
Discussion started by: satinet
0 Replies
2. AIX
How to check the ntpd version of AIX 5.3 ? (3 Replies)
Discussion started by: alanlkw
3 Replies
3. Shell Programming and Scripting
I need to replace the line daemon ntpd $OPTIONS in the following script with daemon ntpd $OPTIONS 2>&1 > /var/log/ntpd.log &
what will happen?
The idea of replacing is to capture the output on the console into ntpd.log file.
Will this work?
... (1 Reply)
Discussion started by: naive1977
1 Replies
4. Red Hat
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)
Discussion started by: ahmad.zuhd
6 Replies
5. Debian
on every boot, ntpd takes long time to start (after moving from dhcp to static ip). is there a way to speed it up? (1 Reply)
Discussion started by: orange47
1 Replies
LEARN ABOUT DEBIAN
chrony
CHRONY(1) User's Manual CHRONY(1)
NAME
chrony - programs for keeping computer clocks accurate
SYNOPSIS
chronyc [OPTIONS]
chronyd [OPTIONS]
DESCRIPTION
chrony is a pair of programs for keeping computer clocks accurate. chronyd is a background (daemon) program and chronyc is a command-line
interface to it. Time reference sources for chronyd can be RFC1305 NTP servers, human (via keyboard and chronyc), or the computer's real-
time clock at boot time (Linux only). chronyd can determine the rate at which the computer gains or loses time and compensate for it while
no external reference is present. Its use of NTP servers can be switched on and off (through chronyc) to support computers with dial-
up/intermittent access to the Internet, and it can also act as an RFC1305-compatible NTP server.
USAGE
chronyc is a command-line interface program which can be used to monitor chronyd's performance and to change various operating parameters
whilst it is running.
chronyd's main function is to obtain measurements of the true (UTC) time from one of several sources, and correct the system clock accord-
ingly. It also works out the rate at which the system clock gains or loses time and uses this information to keep it accurate between mea-
surements from the reference.
The reference time can be derived from either Network Time Protocol (NTP) servers, reference clocks, or wristwatch-and-keyboard (via
chronyc). The main source of information about the Network Time Protocol is http://www.eecis.udel.edu/~ntp.
It is designed so that it can work on computers which only have intermittent access to reference sources, for example computers which use a
dial-up account to access the Internet. Of course, it will work on computers with permanent connections too.
In addition, for Linux 2.0.x (for x >= 32) or 2.2 onwards, chronyd can monitor the system's real time clock performance, so the system can
maintain accurate time even across reboots.
Typical accuracies available between 2 machines are
On an ethernet LAN : 100-200 microseconds, often much better On a V32bis dial-up modem connection : 10's of milliseconds (from one session
to the next)
With a good reference clock the accuracy can reach one microsecond.
chronyd can also operate as an RFC1305-compatible NTP server and peer.
SEE ALSO
chronyc(1), chrony(1)
http://chrony.tuxfamily.org/
AUTHOR
Richard Curnow <rc@rc0.org.uk>
This man-page was written by Jan Schaumann <jschauma@netmeister.org> as part of "The Missing Man Pages Project". Please see
http://www.netmeister.org/misc/m2p2/index.html for details.
The complete chrony documentation is supplied in texinfo format.
chrony December 04, 2009 CHRONY(1)