Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
how to configure timed to access to a internet - timeserver
- Thread starter ppauge
- Start date
I get the 'internet time' for my rs/6000 using the following line from within crontab
0 4,8,12,16,20 * * * /usr/sbin/ntpdate 172.27.1.1 time.nist.gov 1>/dev/null 2>/dev/nul
This checks and set the time 5 times a day. Please note that 172.27.1.1 is my local router that HAS the correct internet time.
There are more options for ntpdate, but these work for me.
do a
man ntpdate
for more info
-Mike Wendling
0 4,8,12,16,20 * * * /usr/sbin/ntpdate 172.27.1.1 time.nist.gov 1>/dev/null 2>/dev/nul
This checks and set the time 5 times a day. Please note that 172.27.1.1 is my local router that HAS the correct internet time.
There are more options for ntpdate, but these work for me.
do a
man ntpdate
for more info
-Mike Wendling
There's four steps that are needed to automatically set your time to the Internet time servers.
Step 1: You want to create/modify the /etc/ntp.conf file to contain references to the Internet time servers. Here's a sample:
====================================================
# Notes:
# Stratum-1 = Internet Time Servers
# Stratum-2 = Your systems with Internet Access
# Stratum-5 = Your Stratum-2 systems, as they see themselves
# Stratum-8 = Other systems that will pull time from your Stratum-2 servers
# Define the Stratum-1 Internet time sources
server 192.5.41.209 # US Navy (ntp2.usno.navy.mil)
server 192.5.41.41 # US Navy (tock.usno.navy.mil)
server 192.5.41.40 # US Navy (tick.usno.navy.mil)
# Local Server for ability to synchronize with internal systems
server 127.127.1.1 # Loads the pseudo-clock driver
# If you have other systems in your network that you want to have serve as peers, add
peer 10.0.0.3 # System Y on our network
peer 10.0.0.4 # System Z on our network
# The "fudge factor" forces the local system to refer to itself as a time of last resort
fudge 127.127.1.1 stratum 5
# This is where the calculated drift is stored, to speed up time sync at boot
driftfile /etc/ntp.drift
# This is where the trace file is located
tracefile /etc/ntp.trace
====================================================
If you have other systems that you will be running as peers, you will want to assign them different Internet time sources, for failover purposes. Your peers would then change to represent the IP addresses of system X and Y (or X and Z)... assuming three systems.
Step 2: Once this file is configured, the /etc/rc.tcpip file needs to be modified to start up the ntp daemon upon system boot (un-comment the line):
# Start up NTP daemon
start /usr/sbin/xntpd "$src_running"
Step 3: You can then run the "ntpdate" command to bring the time close to reliable
Step 4: Start the ntp daemon, via the command "startsrc -s xntpd" (when logged in as root).
To query the progress of time keeping, run "ntpq -p" as root.
I generally have my three production systems serve as Stratum-2 time servers, and have my development servers (Stratum-8) refer to the production servers for their time (as Stratum-5). If you would like the development system configuration, just let me know!
I hope this helps!
Barbara Jo
UNIX Systems Administrator
BarbaraJo.Palsa@vhda.com
Step 1: You want to create/modify the /etc/ntp.conf file to contain references to the Internet time servers. Here's a sample:
====================================================
# Notes:
# Stratum-1 = Internet Time Servers
# Stratum-2 = Your systems with Internet Access
# Stratum-5 = Your Stratum-2 systems, as they see themselves
# Stratum-8 = Other systems that will pull time from your Stratum-2 servers
# Define the Stratum-1 Internet time sources
server 192.5.41.209 # US Navy (ntp2.usno.navy.mil)
server 192.5.41.41 # US Navy (tock.usno.navy.mil)
server 192.5.41.40 # US Navy (tick.usno.navy.mil)
# Local Server for ability to synchronize with internal systems
server 127.127.1.1 # Loads the pseudo-clock driver
# If you have other systems in your network that you want to have serve as peers, add
peer 10.0.0.3 # System Y on our network
peer 10.0.0.4 # System Z on our network
# The "fudge factor" forces the local system to refer to itself as a time of last resort
fudge 127.127.1.1 stratum 5
# This is where the calculated drift is stored, to speed up time sync at boot
driftfile /etc/ntp.drift
# This is where the trace file is located
tracefile /etc/ntp.trace
====================================================
If you have other systems that you will be running as peers, you will want to assign them different Internet time sources, for failover purposes. Your peers would then change to represent the IP addresses of system X and Y (or X and Z)... assuming three systems.
Step 2: Once this file is configured, the /etc/rc.tcpip file needs to be modified to start up the ntp daemon upon system boot (un-comment the line):
# Start up NTP daemon
start /usr/sbin/xntpd "$src_running"
Step 3: You can then run the "ntpdate" command to bring the time close to reliable
Step 4: Start the ntp daemon, via the command "startsrc -s xntpd" (when logged in as root).
To query the progress of time keeping, run "ntpq -p" as root.
I generally have my three production systems serve as Stratum-2 time servers, and have my development servers (Stratum-8) refer to the production servers for their time (as Stratum-5). If you would like the development system configuration, just let me know!
I hope this helps!
Barbara Jo
UNIX Systems Administrator
BarbaraJo.Palsa@vhda.com
- Status