02-03-2005
I think the differences in time (8 minutes) is just too much for ntp to handle - you need to sync by changing the time on the client side and then start up your ntp - although this isn't stated in the
documentation for clients, seeing some of the problems with large time differences between ntp servers it's possible.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
All
What is the best way to keep the system clock synchronized? I have looked at ntp and netdate. Is one good over the other? Basically I want to know if what is the most secure way to keep the system clock insync. netdate will require me to open up some port 37... is this safe? ntp also... (1 Reply)
Discussion started by: skotapal
1 Replies
2. AIX
I want to synchronize my AIX 5.3 server with the server NTP windows using the ntpdate commande but there was a difference about 9 hours after synchro. here is my script and the result
# date
Tue Apr 10 18:58:06 CDT 2007
# ntpdate 192.168.10.212
10 Apr 09:58:19 ntpdate: step time server... (5 Replies)
Discussion started by: tovohery
5 Replies
3. Shell Programming and Scripting
I want to do a synchronization from local to ftp.
local:
name modified time
a.txt 10:04
c.txt 10:05
ftp:
b.txt 10:00
c.txt 10:05
final result would be
a.txt copy to ftp
b.txt deleted
c.txt nothing to do
Is there a good way to do so?
Thanks. (3 Replies)
Discussion started by: uativan
3 Replies
4. Shell Programming and Scripting
Hi guys and girls :)
I have some problem with folder synchronization.
I have a hudson job that make special build from svn data (check outing full project every time), after build folder is synchronized with second folder lets call them build and destination :)
Currently I'm copying build to... (1 Reply)
Discussion started by: cvi
1 Replies
5. Red Hat
hello all,,
am trying to do a time synchronization between a ntp server and a client, but facing some problems in doing so:
i run the ntpdate in debug mode and this is what i got. please help me out..
# ntpd -d -u 172.22.1.207
ntpd 4.2.2p1@1.1570-o Sun Aug 28 19:21:03 UTC 2011 (1)... (1 Reply)
Discussion started by: rahul11c
1 Replies
6. Red Hat
Good morning,
My first post and first visit, so hello. I have been asked to see if one of our Linux boxes can have it's time sync automatically because the person who built the system has told our staff it cannot be done. To me that raised some flags because although I am no Linux expert, I just... (12 Replies)
Discussion started by: YSupport
12 Replies
7. Solaris
Hi everyone!
I wonder about the rsync. The purpose I just want:
synchronization from server 1 to server 2 by rsync, example:
Node 1: /app/logs/*
Node 2: /app/logs/*
in Node 1 when I used rsync -aru /app/logs/ node2:/app/logs/, then everything will be copied and update to node 2. But,... (1 Reply)
Discussion started by: trantuananh24hg
1 Replies
8. Homework & Coursework Questions
Use and complete the template provided. The entire template must be completed. If you don't, your post may be deleted!
1. The problem statement, all variables and given/known data:
it is assumed that the five processes are available according to the graph (cycle is formed of five process). ... (1 Reply)
Discussion started by: mariam40
1 Replies
9. HP-UX
There is one server in my company where the time is out of sync.
When I checked (compared with other servers whose time is correct), the XNTPD variable in /etc/rc.config.d/netdaemons was set as 0.
I changed this to 1, and tried restarting the xntpd process with :
# /sbin/init.d/xntpd start
... (4 Replies)
Discussion started by: anaigini45
4 Replies
10. UNIX for Advanced & Expert Users
Hello,
one of my clients has the following task for me:
To write a Perl script that checks, whether ntp is active on a particular AIX or Linux box.
Obviously the last synchronization is logged in the file ntp.log
So, my task would be find out, when the synchronization SHOULD have taken... (1 Reply)
Discussion started by: Bloehdian1
1 Replies
NTP(8) System Manager's Manual NTP(8)
NAME
ntp - query an ntp clock
SYNOPSIS
ntp [-v] [-s] [-f] hosts...
DESCRIPTION
ntp sends an ntp packet to the ntp daemon running on each of the given hosts. A daemon fills in fields of the ntp packet as per RFC-????
and sends the packet back. ntp then formats and prints the result on the standard output.
The default output shows the delay, offset, and date in ctime() format.
Options can reset the time of the local system clock.
OPTIONS
-v Verbose output, showing the full contents of received ntp packets, plus caluclated offset, displacement, etc.
-s Set system time-of-day clock. Will only happen if time offset is less than compiled-in constant WAYTOBIG (currently 1000 seconds).
Will not happen if remote host is unsynchronized.
-f Force setting system clock regardless of offset. Must be used with -s option. Still will not reset clock if remote system is
unsynchronized.
NTP RESULTS
The default output for each host looks like this:
128.8.10.1: delay:1.845207 offset:-0.358460 Mon Mar 20 08:05:44 1989
The verbose output for each host looks like this:
Packet from: [128.8.10.1]
Leap 0, version 1, mode Server, poll 6, precision -10 stratum 1 (WWVB)
Synch Distance is 0000.1999 0.099991
Synch Dispersion is 0000.0000 0.000000
Reference Timestamp is a7bea6c3.88b40000 Tue Mar 7 14:06:43 1989
Originate Timestamp is a7bea6d7.d7e6e652 Tue Mar 7 14:07:03 1989
Receive Timestamp is a7bea6d7.cf1a0000 Tue Mar 7 14:07:03 1989
Transmit Timestamp is a7bea6d8.0ccc0000 Tue Mar 7 14:07:04 1989
Input Timestamp is a7bea6d8.1a77e5ea Tue Mar 7 14:07:04 1989
umd1: delay:0.019028 offset:-0.043890 Tue Mar 7 14:07:04 1989
The various fields are interpreted as follows:
Packet from: [address]
The address that this ntp packet was received from.
Leap indicator: n
The leap second indicator. Non-zero if there is to be a leap second added or subtracted at the new year.
Status: n
Stratum: n (source)
The stratum of the clock in the NTP hierarchy, along with the source of the clock, either the name of a reference standard (such as
WWVB or GOES) or the Internet address of the clock that this clock is derived from.
Poll = n
The desired poll rate of the peer.
Precision = exponent (dec)
The claimed precision of the clock, in seconds.
Synchronizing Dist is ???
Synchronizing Dispersion is ???
The next five timestamps are given as NTP fixed-point values, in both hexadecimal and ctime(3). These are set either by this ntp process,
or by the server we are quering.
Reference Timestamp is hex-timestamp ctime string
The last time the server clock was adjusted. (remote time)
Originate Timestamp is hex-timestamp ctime string
When the ntp request was transmitted by us to the server. (local time)
Receive Timestamp is hex-timestamp ctime string
When the ntp request was received at the server. (remote time)
Transmit Timestamp is hex-timestamp ctime string
When the ntp response was transmitted by the server. (remote time)
Input Timestamp is hex-timestamp ctime string
When the ntp response was received by us. (local time)
hostname: delay:time offset:time
The summary of the results of the query, giving the hostname of the responding clock (from the command line), the round-trip delay,
and the offset between the two clocks (assuming symmetric round-trip times).
BUGS
Using ntp with the current host will show inaccurate results.
Probably a few others. Report bugs to Louis A. Mamokos (louie@trantor.umd.edu).
SEE ALSO
RFC-???? Network Time Protocol(1), Dave Mills and ...
ntpd(8), ntpdc(8)
30 July 1988 NTP(8)