Sponsored Content
Operating Systems Solaris Execute the ntpdate command only when NTP daemon is stopped? Post 302738909 by Neo on Monday 3rd of December 2012 05:50:31 AM
Old 12-03-2012
From my experience, unless you are running an NTP server to synchronize your own devices against that reference (your NTP server) then, you are better off running ntpdate in a crontab to keep your time in sync.

On the other hand, if you are managing a large organization, then you should run one or more NTP servers in your organization and they all the devices and hosts within your organization should sync to your internal servers as a matter of policy.

There are many reasons for this. First of all, your internal devices will be closes in time-sync if the network-distance to their NTP servers are relatively the same. Second, it is better "net etiquette" to have a handful of devices (ntpd processes) sync with external time services versus every device in the organization.

Also, when external NTP servers change, it is only necessary to update the main time servers in a organization. There are more reasons, but you get the idea.

On the other hand, if you are not a member of a large (or even medium or smallish) organization and are just syncing your computer; then ntpdate is all you should ever need. Just run it in your cron files.

The most important thing, of course, is to insure you system clocks on all devices are in time sync, so your log files and process times are also in sync.
This User Gave Thanks to Neo 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
ntpdate(1M)						  System Administration Commands					       ntpdate(1M)

NAME
ntpdate - set the date and time by way of NTP SYNOPSIS
/usr/sbin/ntpdate [-bBdoqsuv] [-a key#] [-e authdelay] [-k keyfile] [-m] [-o version] [-p samples] [-t timeout] [-w] server... DESCRIPTION
The ntpdate utility sets the local date and time. To determine the correct time, it polls the Network Time Protocol (NTP) servers on the hosts given as arguments. This utility must be run as root on the local host. It obtains a number of samples from each of the servers and applies the standard NTP clock filter and selection algorithms to select the best of these. The reliability and precision of ntpdate improve dramatically with a greater number of servers. While a single server may be used, better performance and greater resistance to inaccuracy on the part of any one server can be obtained by providing at least three or four servers, if not more. The ntpdate utility makes time adjustments in one of two ways. If it determines that your clock is off by more than 0.5 seconds it simply steps the time by calling gettimeofday(3C). If the error is less than 0.5 seconds, by default, it slews the clock's time with the offset, by way of a call to adjtime(2). The latter technique is less disruptive and more accurate when the offset is small; it works quite well when ntpdate is run by cron every hour or two. The adjustment made in the latter case is actually 50% larger than the measured offset. This adjustment tends to keep a badly drifting clock more accurate, at some expense to stability. This tradeoff is usually advantageous. At boot time, however, it is usually better to step the time. This can be forced in all cases by specifying the -b option on the command line. The ntpdate utility declines to set the date if an NTP server daemon like xntpd(1M) is running on the same host. It can be run on a regular basis from cron(1M) as an alternative to running a daemon. Doing so once every one to two hours results in precise enough timekeeping to avoid stepping the clock. OPTIONS
The following options are supported: -a key# Authenticate transactions, using the key number, key#. -b Step the time by calling gettimeofday(3C). -B Force the time to always be slewed using the adjtime(2) system call, even if the measured offset is greater than +-128 ms. The default is to step the time using settimeofday(3C) if the offset is greater than +-128 ms. If the offset is much greater than +-128 ms in this case, that it can take a long time (hours) to slew the clock to the correct value. During this time the host should not be used to synchronize clients. -d Display what will be done without actually doing it. Information useful for general debugging is also printed. -e authdelay Specify an authentication processing delay, authdelay in seconds. See xntpd(1M) for details. This number is usually small enough to be negligible for purposes of ntpdate. However, specifying a value may improve timekeeping on very slow CPU's. -k keyfile Read keys from the file keyfile instead of the default file, /etc/inet/ntp.keys. keyfile should be in the format described in xntpd(1M). -m Join multicast group specified in server and synchronize to multicast NTP packets. The standard NTP group is 224.0.1.1. -o version Force the program to poll as a version 1 or version 2 implementation. By default ntpdate claims to be an NTP version 3 implementation in its outgoing packets. However, some older software declines to respond to version 3 queries. This option can be used in these cases. -p samples Set the number of samples ntpdate acquires from each server. samples can be between 1 and 8 inclusive. The default is 4. -q Query only. Do not set the clock. -s Log actions by way of the syslog(3C) facility rather than to the standard output -- a useful option when running the pro- gram from cron(1M). -t timeout Set the time ntpdate spends, waiting for a response. timeout is rounded to a multiple of 0.2 seconds. The default is 1 sec- ond, a value suitable for polling across a LAN. -u Use an unprivileged port to send the packets from. This option is useful when you are behind a firewall that blocks incom- ing traffic to privileged ports, and you want to synchronize with hosts beyond the firewall. The -d option always uses unprivileged ports. -v Be verbose. This option causes ntpdate's version identification string to be logged. -w Wait until able to synchronize with a server. When the -w option is used together with -m, ntpdate waits until able to join the group and synchronize. FILES
/etc/inet/ntp.keys Contains the encryption keys used by ntpdate. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWntpu | +-----------------------------+-----------------------------+ SEE ALSO
cron(1M), xntpd(1M), adjtime(2), gettimeofday(3C), settimeofday(3C)syslog(3C), attributes(5) NOTES
The technique of compensating for clock oscillator errors to improve accuracy is inadequate. However, to further improve accuracy would require the program to save state from previous runs. SunOS 5.11 29 Sep 1999 ntpdate(1M)
All times are GMT -4. The time now is 08:29 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy