Sponsored Content
Operating Systems Linux my server is 1 hour behind after DST Post 302255540 by chatwizrd on Thursday 6th of November 2008 03:54:11 PM
Old 11-06-2008
So try ntpdate to sync your clock.

# ntpdate pool.ntp.org
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

an hour less in 24 hour system

My program: __________________________________ #!/bin/ksh DAY=`date +%y%m%d` H=`date +%H` M=`date +%M` day=`date +%m/%d/%y` let h=$H-1 echo DAY $DAY echo H $H echo M $M echo day $day echo h $h _____________________________________ My result: (3 Replies)
Discussion started by: bobo
3 Replies

2. Solaris

DST on Solaris 2.6/7

I have several servers that are outside the country and are running Solaris 6 mainly with a few Solaris 7 boxes here and there. Because of that, we need to schedule time to change the time on March 11th and again in April, October and November. At least until the customer decides it's time to... (3 Replies)
Discussion started by: BOFH
3 Replies

3. SCO

DST script for 5.0.0

I checked SCO's site for DST fix for SCO 5.0.0 and there iis not one available. Can I run a script in the cron to read in and change the time? TiA (2 Replies)
Discussion started by: tbgeek
2 Replies

4. SCO

Dst - V 3.6.3

Hello, Anyone know where I can find the DST updates for SCO Xdesktop 3.6.3? Thanks (0 Replies)
Discussion started by: ddzc
0 Replies

5. UNIX for Dummies Questions & Answers

How to verify DST Update

Hello, Does anyone know how can I verify if the DST update on a SCO Unixware system has been installed successfully? UNIXWARE 7.1.4 MP3 Looking forward to some help, please.... Thanks (8 Replies)
Discussion started by: Yorgy
8 Replies

6. AIX

AIX and DST

Just a quick last minute thing here. AIX 5.1. I ran the perl script referenced in the tutorials and found the AIX box is triggering DST on the 14th instead of the 11th. The 5.2 boxes come back with the right answers. The DST patches have been applied (or I'd have Apr 1st instead of the 14th). ... (0 Replies)
Discussion started by: BOFH
0 Replies

7. Solaris

DST Patch

How to update DST patch. Whatat are the necessary steps that have to be taken on the servers to update this patch?. (1 Reply)
Discussion started by: sandeepkv
1 Replies

8. UNIX for Advanced & Expert Users

How to set NTP server to +1 hour time?

Hello, colleges! I need to synchronize time on several thousands device (UTM-1 Edge Appliances - All inclusive, all secure, all branch offices.) which don`t understand summer time at all. But in my country summer time are used. I plan to sync it with NTP server with modificated time: plus one... (2 Replies)
Discussion started by: chmelvv
2 Replies

9. Shell Programming and Scripting

Determine if given date is in DST

Is there a way to figure out if given date is in DST or in EST? So imagine a shell script is_date_dst.sh sh is_date_dst.sh 2009-03-02 would return 0 and sh is_date_dst.sh 2009-03-22 would return 1 This script should not assume the timezone of the machine it runs on, but only the date passed... (7 Replies)
Discussion started by: asriva
7 Replies

10. Shell Programming and Scripting

How to convert 24 hour time to 12 hour timing?

Hi friends, I want to convert 24 hour timing to 12 hour please help me... my data file looks like this.. 13-Nov-2011 13:27:36 15.32044 72.68502 13-Nov-2011 12:08:31 15.31291 72.69807 16-Nov-2011 01:16:54 15.30844 72.74028 15-Nov-2011 20:09:25 15.35096 ... (13 Replies)
Discussion started by: nex_asp
13 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 07:45 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy