09-11-2009
To keep the forums high quality for all users, please take the time to format your posts correctly.
First of all, use Code Tags when you post any code or data samples so others can easily read your code. You can easily do this by highlighting your code and then clicking on the # in the editing menu. (You can also type code tags [code] and [/code] by hand.)
Second, avoid adding color or different fonts and font size to your posts. Selective use of color to highlight a single word or phrase can be useful at times, but using color, in general, makes the forums harder to read, especially bright colors like red.
Third, be careful when you cut-and-paste, edit any odd characters and make sure all links are working property.
Thank You.
The UNIX and Linux Forums
10 More Discussions You Might Find Interesting
1. Windows & DOS: Issues & Discussions
All,
I have a Windows XP client which I need to get time synchronized from a Linux ntp server. What are the commands to perform the setup and configuration?
Thanks,
Mike (1 Reply)
Discussion started by: bubba112557
1 Replies
2. Solaris
All,
How do you set a Solaris 9 server which received ntp updates from a ntp server to broadcast them on a local subnet. I have created a /etc/inet/ntp.conf file to receive the updates from a server on network and need to make this server become like a ntp relay from the main server.
Any... (1 Reply)
Discussion started by: bubba112557
1 Replies
3. AIX
Hello everybody! When I run command "ntpdate" the following error occures
"ksh: ntpdate: 0403-006 Execute permission denied.
"
# oslevel -s
5300-08-06-0918
oslevel -r
5300-08
eny suggestion friends? :-) (3 Replies)
Discussion started by: wwwzviadi
3 Replies
4. Linux
I need to configure an NTP daemon on a "bridge-PC" connected on 2 LANs. It is expected to read the correct time on a time server on the first LAN and behave as a server for the second LAN.
Can I do both the things with ntpd?
In other words, is ntpd able to work as client and server at the same... (3 Replies)
Discussion started by: bigjim33
3 Replies
5. Solaris
Hi, I am trying to configure NTP client on my Solaris server, but I am getting error like:
Jan 13 10:53:33 SPOTS ntpdate: no server suitable for synchronization foundMy ntp.conf file:
bash-3.00# pwd
/etc/inet
bash-3.00#
bash-3.00#
bash-3.00# cat ntp.conf
# ident "@(#)ntp.client... (5 Replies)
Discussion started by: nypreH
5 Replies
6. Solaris
How to add offset to NTP client so that, for eg., clock is -20 seconds? (2 Replies)
Discussion started by: orange47
2 Replies
7. HP-UX
Hi
I wonder if its possible to setup NTP clients running HP-UX o.s. from a solaris 10 NTP server?
FR (3 Replies)
Discussion started by: fretagi
3 Replies
8. Solaris
hi all
ntp client side configuration file is done but in
# ntpq -p
remote refid st t when poll reach delay offset disp
==============================================================================
ntpserver .INIT. 16 u - 64 0 0.00 0.000... (5 Replies)
Discussion started by: nikhil kasar
5 Replies
9. Red Hat
Hi,
I have two ntp servers in my cluster and I want all the nodes in my cluster to sync with either of the ntp servers or just one. Unfortunately it keep rotating the sync, between my ntp server 1, ntp server 2 and local. Is there anyway I can change the sync to avoid local?
# ntpq -p
... (3 Replies)
Discussion started by: pjeedu2247
3 Replies
10. Programming
Was not really happy with the NTP clients for the ESP8266 because, after a few years of game engine programming, I am not a fan of a lot of code and delays in the main loop, so here is a "slightly better NTP client" for the ESP8266.
In a nutshell, instead of having a delay in the main loop as a... (1 Reply)
Discussion started by: Neo
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)