Sponsored Content
Operating Systems Linux Red Hat NTPD service restart and time synch Post 302992729 by rbatte1 on Wednesday 1st of March 2017 05:24:54 AM
Old 03-01-2017
If you have the NTP configuration correct, then I would use ntpdate timeserver to get the clock to jump to the correct time. Remember that this will set the system clock to CUT/UTC/GMT/ZULU and it is the timezone that changes the displayed date. You may be changing the date to what looks correct, but it is too far out for NTP to then follow the external source. NTP always follows the zero timezone.



Does this help?

Robin
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Service Restart Netbackup

For vertitas netbackup 6.0 I have media server :Solaris Client server: Windows I want to restart the netbackup service on the media server . plz suggest ASAP. (1 Reply)
Discussion started by: saurabh84g
1 Replies

2. Shell Programming and Scripting

Restart a Service!!

Hello, I am trying to write a script which will monitor few processes(winbind) for cpu utilization, If the process consumes more than say 99% cpu for 3 minutes, I want to run a script to restart the service which forks the process. ---------- Post updated at 11:21 AM ---------- Previous update... (5 Replies)
Discussion started by: linuxaddict7
5 Replies

3. HP-UX

Script to auto restart a service

Hi All, May i please know if it is possible to write a script to check the log messages and automatically restart a service if it is failed or it is stopped. Appreciate your suggestions. Thanks in advance. regards, Eajaz (2 Replies)
Discussion started by: ajazshariff
2 Replies

4. Shell Programming and Scripting

Need to Restart Service with Password

Hi All, Requirement : I need to check for some services in my environment and restart the service if its not running. I have written script to check the script if its running or not. While if its not running i need to restart it using ./start command. But it will ask for password prompt and i... (4 Replies)
Discussion started by: pradeepbaliga
4 Replies

5. Shell Programming and Scripting

how to synch 2 processes to start at the same time

Hey Excuse me if this question is repeated everywhere but I am still new with scripting and I couldn't apply what I found to my case :confused::confused: I am trying to run a rec process on a ssh client and at the same time play a file from my computer so i tried this #!/bin/bash echo... (3 Replies)
Discussion started by: Antaha
3 Replies

6. SuSE

Service restart daily

Hi, Beside using crontab, what is other application we can set it? Normally I check using command crontab -l. Any other path I need to check? Please guide me. Thanks. (2 Replies)
Discussion started by: mzainal
2 Replies

7. Red Hat

Service restart and check if running

Hello, I'l like to create a script that restart a service (/etc/init.d/httpd restart) and also check if after restart the service is actually running. Sometimes it happen that at the first try the service fails to restart. Thanks (2 Replies)
Discussion started by: bazzola
2 Replies

8. Red Hat

Restart service xinit.d or init.d ?

Hello How do I restart init.d ?? (centos 6.5) Thanks (2 Replies)
Discussion started by: mnnn
2 Replies

9. Red Hat

Apache service not coming up after restart

When I update the server with new SSL certificates, and restart httpd, I get errors : # service httpd restart Stopping httpd: rm: cannot remove `/usr/local/apache2/bin/httpd/logs/httpd.pid': Not a directory Starting httpd: ... (0 Replies)
Discussion started by: anaigini45
0 Replies

10. Shell Programming and Scripting

Time synch monitoring

I'm using a debian variant. My system clock already auto synchronizes. I'd like to have some sort of alert or log entry if the time is ever off by more than a particular amount. My first choice is to have a new file created on the desktop each day that there is a slip greater than the specified... (4 Replies)
Discussion started by: jutnobs
4 Replies
NTPDATE(8)						    BSD System Manager's Manual 						NTPDATE(8)

NAME
ntpdate -- set the date and time via NTP SYNOPSIS
ntpdate [-46bBdoqsuv] [-a key] [-e authdelay] [-k keyfile] [-o version] [-p samples] [-t timeout] server ... DESCRIPTION
Note: The functionality of this program is now available in the ntpd(8) program. See the -q command line option in the ntpd(8) page. After a suitable period of mourning, the ntpdate utility is to be retired from this distribution. The ntpdate utility sets the local date and time by polling the Network Time Protocol (NTP) server(s) given as the server arguments to deter- mine the correct time. It must be run as root on the local host. A number of samples are obtained from each of the servers specified and a subset of the NTP clock filter and selection algorithms are applied to select the best of these. Note that the accuracy and reliability of ntpdate depends on the number of servers, the number of polls each time it is run and the interval between runs. The following options are available: -4 Force DNS resolution of following host names on the command line to the IPv4 namespace. -6 Force DNS resolution of following host names on the command line to the IPv6 namespace. -a key Enable the authentication function and specify the key identifier to be used for authentication as the argument key. The keys and key identifiers must match in both the client and server key files. The default is to disable the authentication function. -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(2) if the offset is greater than +-128 ms. Note that, if the offset is much greater than +-128 ms in this case, 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. -b Force the time to be stepped using the settimeofday(2) system call, rather than slewed (default) using the adjtime(2) system call. This option should be used when called from a startup file at boot time. -d Enable the debugging mode, in which ntpdate will go through all the steps, but not adjust the local clock. Information useful for general debugging will also be printed. -e authdelay Specify the processing delay to perform an authentication function as the value authdelay, in seconds and fraction (see ntpd(8) for details). This number is usually small enough to be negligible for most purposes, though specifying a value may improve timekeeping on very slow CPU's. -k keyfile Specify the path for the authentication key file as the string keyfile. The default is /etc/ntp.keys. This file should be in the format described in ntpd(8). -o version Specify the NTP version for outgoing packets as the integer version, which can be 1 or 2. The default is 3. This allows ntpdate to be used with older NTP versions. -p samples Specify the number of samples to be acquired from each server as the integer samples, with values from 1 to 8 inclusive. The default is 4. -q Query only - do not set the clock. -s Divert logging output from the standard output (default) to the system syslog(3) facility. This is designed primarily for conve- nience of cron(8) scripts. -t timeout Specify the maximum time waiting for a server response as the value timeout, in seconds and fraction. The value is rounded to a mul- tiple of 0.2 seconds. The default is 1 second, a value suitable for polling across a LAN. -u Direct ntpdate to use an unprivileged port for outgoing packets. This is most useful when behind a firewall that blocks incoming traffic to privileged ports, and you want to synchronise with hosts beyond the firewall. Note that the -d option always uses unpriv- ileged ports. -v Be verbose. This option will cause ntpdate's version identification string to be logged. The ntpdate utility can be run manually as necessary to set the host clock, or it can be run from the host startup script to set the clock at boot time. This is useful in some cases to set the clock initially before starting the NTP daemon ntpd(8). It is also possible to run ntpdate from a cron(8) script. However, it is important to note that ntpdate with contrived cron(8) scripts is no substitute for the NTP daemon, which uses sophisticated algorithms to maximize accuracy and reliability while minimizing resource use. Finally, since ntpdate does not discipline the host clock frequency as does ntpd(8), the accuracy using ntpdate is limited. Time adjustments are made by ntpdate in one of two ways. If ntpdate determines the clock is in error more than 0.5 second it will simply step the time by calling the system settimeofday(2) routine. If the error is less than 0.5 seconds, it will slew the time by calling the system adjtime(2) routine. The latter technique is less disruptive and more accurate when the error is small, and works quite well when ntpdate is run by cron(8) every hour or two. The ntpdate utility will decline to set the date if an NTP server daemon (e.g., ntpd(8)) is running on the same host. When running ntpdate on a regular basis from cron(8) as an alternative to running a daemon, doing so once every hour or two will result in precise enough time- keeping to avoid stepping the clock. Note that in contexts where a host name is expected, a -4 qualifier preceding the host name forces DNS resolution to the IPv4 namespace, while a -6 qualifier forces DNS resolution to the IPv6 namespace. If NetInfo support is compiled into ntpdate, then the server argument is optional if ntpdate can find a time server in the NetInfo configura- tion for ntpd(8). FILES
/etc/ntp.keys contains the encryption keys used by ntpdate. SEE ALSO
ntpd(8) BUGS
The slew adjustment is actually 50% larger than the measured offset, since this (it is argued) will tend to keep a badly drifting clock more accurate. This is probably not a good idea and may cause a troubling hunt for some values of the kernel variables kern.clockrate.tick and kern.clockrate.tickadj. BSD
May 17, 2006 BSD
All times are GMT -4. The time now is 02:26 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy