Sponsored Content
Operating Systems Linux Red Hat Auto NTP Time Synchronization Post 302581634 by YSupport on Tuesday 13th of December 2011 03:46:53 PM
Old 12-13-2011
Quote:
Originally Posted by mark54g
That seems like such a convoluted way to use NTP, which actually DOES sync time automatically.

Normally, you would just run ntpd and synchronize to a time server, rather than slamming the clock and creating additional drift.
So mark54g how would your suggestion of running ntpd be utilized on our system then to automatically keep the system continually synchronized because right now they are having to on monthly basis resync cause it drifts 3-4 minutes out. Using the same kind of crontab command to set up the scheduling? Thanks.
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

ntp across time zones

I've been tasked to implement ntp on my SCO Unix servers. I have over 600 servers spread across the US in different time zones. Each remote server has network connectivity to a main server here, through their local ISP. (That's how we currently deliver mail to them). My question is, how can... (5 Replies)
Discussion started by: Howeird
5 Replies

2. UNIX for Dummies Questions & Answers

Time synchronization

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

3. HP-UX

NTP time

Is anyone familiar with adding NTP timing to a HPUX 10 OS? Thanks Brian (2 Replies)
Discussion started by: breigner
2 Replies

4. UNIX for Advanced & Expert Users

time synchronization

i have an HP UNIX box w/c acts as ntp server... I tried to change the time plus 8 minutes... the problem is that the other HP UNIX ntp client did not follow the time... when I tried to restart ntp client... using stop start it only sync to the server once... when I issue the command "ntpq -p", w/c... (2 Replies)
Discussion started by: inquirer
2 Replies

5. AIX

NTP - with time difference

We have configured most of 1200 servers with an NTP server. For the rest of the servers, I have a strange requirement. I want to synchronize them with NTP time with a lag of 15 minutes. Is it possible ? If yes How ? (0 Replies)
Discussion started by: shauche
0 Replies

6. Linux

How often does Linux NTP server update its time with the external NTP server?

All here, thank you for listening. Now I've set up a Linux NTP server by adding a external windows NTP server in /etc/ntp.conf. Then I start the ntpd daemon. But how often does the Linux NTP server update its time with the external NTP server? I've looked up everywhere but found no information... (1 Reply)
Discussion started by: MichaelLi
1 Replies

7. Red Hat

ntp time synchronization

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

8. AIX

NTP time problem

I got an ntp time problem on AIX server. os version is AIX7.1 OS LEVEL 7.1.0.0 i got below output,when i run the below command bash-3.2# ntpdate -dv XXXXXXXXXXXXXXXXXXXXXXXX 4 Dec 12:50:49 ntpdate: 3.4y transmit(xxxxxxxxx) receive(xxxxxxxxx) transmit(xxxxxxxx) receive(xxxxxxxxx)... (9 Replies)
Discussion started by: murali969
9 Replies

9. HP-UX

Ntp time synchronization problems

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

Ntp : How is the synchronization time scheduled?

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
PACEMAKER(8)						    BSD System Manager's Manual 					      PACEMAKER(8)

NAME
pacemaker -- clock drift adjustment daemon SYNOPSIS
pacemaker [-d drift] [-b] [-e error] [-a interval] [-i] [-v] [-n] DESCRIPTION
pacemaker adjusts the system clock periodically to compensate for clock drift. The clock drift is normally computed by ntpd(8), which writes a clock drift value in /var/db/ntp.drift. By default, pacemaker will call adjtime(2) once per second to slew the system clock. The daemon is started by launchd(8) only when the drift file is present or has just been created in the file system. pacemaker detects changes in the file and re-calculates clock adjustment values appropriately. The daemon will exit if the drift file is deleted and is not re-created within one minute. As a fail-safe mechanism, pacemaker will reset the system clock using settimeofday(2) if the system clock requires adjustment exceeding the maximum value that can be accomodated by adjtime to slew the clock. In practice, this extreme case should never occur. The -d option allows the specification of either a floating-point drift value, or the path name of an alternate drift file. If a floating point drift value is specified, pacemaker will use the given value and will not read a drift file. To reduce power consumption, especially when the system is using internal battery power, it may be desirable to reduce the frequency of calls to adjust the system's clock drift. The -e and -a options, together with the -b flag allow several ways to control the clock adjustment fre- quency. The floating point value following -e specifies a maximum error tolerance in seconds for the system clock. For example, a value of 0.001 specifies that the clock drift adjustment should only be done frequently enough to keep the system clock error within one millisecond, based on the current clock drift rate. Alternatively, the clock adjustment frequency can be specified exactly as a value in seconds following -a. When both -e error and -a interval are provided, pacemaker will choose to adjust the system clock either every interval seconds, or less fre- quently if the clock error will remain within error seconds. The settings for -e and/or -a may be specified for operation of the system while using an external power source, and specified independently for operation using internal batteries. By default, the values for -e and/or -a are used for both power configurations. If the -b flag pre- cedes -e and/or -a, then the following settings apply only when the system is using internal battery power. For example, starting pacemaker with the following parameters will cause it to adjust the clock every 2 seconds when the system is using external power. When running on battery power, it will adjust the clock no more than once every 10 seconds, or less frequently if the clock error remains less than five milliseconds. pacemaker -a 2 -b -a 10 -e 0.005 When invoked on the command-line with -i, pacemaker prints a summary of internal parameters and then exits. The -v flag causes pacemaker to print copies of its log messages to standard error. Note that this requires running the program from the command line rather than from launchd. -n causes pacemaker to run without actually attempting to adjust the system clock. FILES
/var/db/ntp.drift default clock drift file SEE ALSO
launchd(8), ntpd(8), adjtime(2), settimeofday(2). HISTORY
The pacemaker daemon was introduced in OS X 10.9. OS X
March 9, 2013 OS X
All times are GMT -4. The time now is 11:40 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy