Sponsored Content
Operating Systems Solaris Execute the ntpdate command only when NTP daemon is stopped? Post 302738855 by fpmurphy on Monday 3rd of December 2012 02:48:30 AM
Old 12-03-2012
Ntpdate adjusts the time on your system in one immediate correction. Ntpd is more subtle; it calculates your system clock drift and continuously adjusts it so that your system maintains more accurate time. Ntpd cannot handle a large clock skew, you need to use ntpdate for that.
This User Gave Thanks to fpmurphy For This Post:
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

NTPDATE Command help

I would like to setup date / time sync on Solaris 8 using the command ntpdate. How do I set it up? Thanks Mark (1 Reply)
Discussion started by: miredale
1 Replies

2. Solaris

How to use Ntpdate to slew the time?

Hi experts, I've a master server which sync to ntp time server daily by using xntpd daemon. Then my client servers will use ntpdate through cron job to synchronize the time hourly. (By using ntpupdate -s -B 'master server') My question is, now I'll need to synchronize to a oracle server which... (2 Replies)
Discussion started by: kenzoo
2 Replies

3. SCO

ntpdate problem in Unixware

Hi Guys, A weird problem. I have disabled ntpd daemon on a HP server and placed ntpdate in crontab instead and redirected the log to a file. This command in cron synchronizes the server with a local time server every 15 minutes. The weird part is that on 3 specific times (5:00 am, 10:00 am,... (2 Replies)
Discussion started by: Verifone
2 Replies

4. UNIX for Dummies Questions & Answers

how execute/visit a site using the cron daemon?

hi, i need to execute/visit a site to check if the site is up or not i have a server that have cron shedule that can execute a php file now how can i execute/visite a site using the same way as i execute a file? thanks a lot for your help :) (1 Reply)
Discussion started by: jasonx22
1 Replies

5. Shell Programming and Scripting

How to replace ntpdate

Hi there, Hi have a group of computers + a server (all debians) connected to each other on a LAN. For some reasons that I've not decided and that I can't change, the computers cannot connect to the net. Moreover, the server has no ntp service. Though, I need to find a way of setting all... (4 Replies)
Discussion started by: chebarbudo
4 Replies

6. Linux

ntp client/daemon sync

All, I need to write a script which can determine if my NTP client is X second off from the NTPD server time. I am looking for a crafty oneliner to calculate the time difference? (3 Replies)
Discussion started by: vada010
3 Replies

7. HP-UX

Setting up NTP HP-UX clients from solaris NTP server

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

Is ntpdate command dependent on ntpd?

Hi, Could someone Please clarify me here: Is ntpdate command a part of ntpd, i mean does ntpdate command a dependent on ntpd? and can ntpdate be run in absence of ntpd service. (5 Replies)
Discussion started by: aksijain
5 Replies

9. Red Hat

Ntp client sync with local over ntp server

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. UNIX for Dummies Questions & Answers

Nohup Command gets status Stopped

Good Morning I need your help please, i tried to execute this script using nohup command but it gets in status stopped nohup ./SapInterfases.sh > SapInterfases.log & prodstg02$ jobs + Stopped(SIGTTOU) nohup ./SapInterfases.sh > SapInterfases.log & I check out log: $ more... (15 Replies)
Discussion started by: alexcol
15 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 03:13 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy