Hi Everyone,
Each time I do update the crontab, it gets reset after exiting from the telnet session. I'm using Solaris 2.8
So it goes like this:
Step 1: Login as root, from a telnet session
Step 2: Crontab -e (I make modification)
Step 3: Save and exit
Step 4: Type crontab -l , changes... (4 Replies)
hi experts,
my requirement is like this i need to develop a shell script to update date part with new incremental date time in file some 'X' which is kept at some server location incrementing every two hours.as i am new to this scripting i need support from u people,thanx in advance (1 Reply)
Hi,
I am trying to display future date from the current date but unable to do so in UNIX (not in PERL). For eg: if today is March 5 then I want a variable wherein I can store Mar 7 date, but unable to get the future date from the current date.
I have tried many possible ways as mentioned below... (11 Replies)
I just installed the latest version of ubuntu and I can't run the update manager without getting an error message. Im not sure what info i need to post so i can get help so just tell me if i need to post info because i would like to use ubuntu. (2 Replies)
hi friends,
I m trying to write a script which compares to dates.
for this i am converting dates into no using synatx
as below
v2=`date | awk '{print $2,$3,$4}'`
v3=`date +%s -d "$v2"`
this syntax is working in bash shell ,but fails in ksh shell.
please suggest on this. (12 Replies)
I have just upgraded to fedora 18 from 17 using fedup tool. The upgradation process succeeded and I can feel the new desktop appearance of fedora18.
when I tried to update using yum update. I can see that the fedora17 files are not removed completely and they are also listed below the files to... (1 Reply)
Hi All,
my requirement is first search the line and updated stg value with the user input value.
ws.rsp.url=https://rt930.rsp-stg.cb.info53.com/RSP/RAFT^M
stg is not fixed string it may varies.So i used the below command for it
rsp=`cat properties | grep ^ws.rsp.url= | awk -F"/"... (1 Reply)
Hi,
I run RHEL 5.2 as a server in my lab. Now the issue I am facing is that I am unable to update my machine using yum update.
It shows an error of missing dependencies though dependencies are already installed.
Please help me to do that.
Error screen shot is also attached. (9 Replies)
I am trying to update an openssl package on my node.
# yum update openssl-1.0.1e-60.el7.x86_64
Loaded plugins: product-id, rhnplugin, subscription-manager
This system is receiving updates from RHN Classic or Red Hat Satellite.
baseline_prd_channel ... (0 Replies)
Discussion started by: Junaid Subhani
0 Replies
LEARN ABOUT OSF1
ntpdate
ntpdate(8) System Manager's Manual ntpdate(8)NAME
ntpdate - set the date and time via NTP (Network Time Protocol)
SYNOPSIS
/usr/sbin/ntpdate [-bdqsuv] [-a key#] [-e authdelay] [-k keyfile] [-o version] [-p samples] [-t timeout] server1 server2 server3...
OPTIONS
Tells ntpdate to step the system time immediately to match NTP. Use this option only when booting the system. Prints configuration and
debugging information. Queries the server(s) and prints the information received; the date and time are not set. Tells ntpdate to log its
actions through the syslog(3) facility rather than to the standard output. This is useful when running the program from cron(8). Tells
ntpdate to use an unprivileged port to send the packets from. This is useful when you are 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 unprivileged ports. Runs
in verbose mode. Specifies that all packets should be authenticated using the key number provided. Specifies an authentication processing
delay, in seconds (see xntpd(8) for details). This number is usually small enough to be negligible for ntpdate's purposes, though specify-
ing a value may improve timekeeping on very slow CPU's. Specifies that authentication keys will be read from keyfile instead of the
default /etc/ntp.keys file. This file should be in the format described in xntpd(8). Forces ntpdate to poll as a version implementation.
By default ntpdate claims to be an NTP version 3 implementation in its outgoing packets. Some older software will decline to respond to
version 3 queries. Acquires a specified number of samples from each server. The range of values for samples is from 1 and 8, inclusive.
The default is 4. Waits timeout seconds for a response. Any value entered will be rounded to a multiple of 0.2 seconds. The default is 1
second, a value suitable for polling across a LAN.
DESCRIPTION
The ntpdate command sets the local date and time by polling the Network Time Protocol server(s) on the host(s) given as 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
the standard NTP clock filter and selection algorithms are applied to select the best of these. The ntpdate command is run from
/sbin/init.d/settime to set the time of day at boot time, if NTP is configured. (See ntpsetup(8) for information on configuring NTP.) Note
that ntpdate's reliability and precision will improve dramatically with greater numbers of servers. While a single server may be used,
better performance and integrity will be obtained by providing at least three or four servers, if not more.
Time adjustments are made by ntpdate in one of the following ways: If ntpdate determines your clock is off by more than 0.5 seconds, it
steps the time by calling settimeofday(2). If the error is less than 0.5 seconds, however, it will by default slew the clock's time by a
call to adjtime(2) with the offset.
The latter technique is less disruptive and more accurate when the offset is small, and 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 since this will tend to keep a badly
drifting clock more accurate (at some expense to stability, though this tradeoff is usually advantageous).
Ntpdate will decline to set the date if an NTP server daemon (for example, xntpd(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 timekeep-
ing to avoid stepping the clock.
Note
Because of significant changes in NTP version 3, you should check all scripts that use the ntpdate command for correct usage and output.
ERRORS
A common problem is polling a server using the wrong query version number or wrong authentication key. If either occurs, ntpdate prints
the following error message: 18 Apr 10:20:28 ntpdate(1192]: no server
suitable for synchronization found
At boot time, if NTP is not configured, the ntpdate prints the following message: WARNING: ntpdate cannot succeed, please check your
NTP configuration
EXAMPLES
The following command line sets the date and time after polling server host1.dec.com as a version 2 implementation: /usr/sbin/ntpdate -o 2
host1.dec.com The following command line sets the date and time after polling server host2.dec.com. All packets are authenticated using
authentication key 1. /usr/sbin/ntpdate -a 1 host2.dec.com
FILES
Specifies the command path Contains the encryption keys used by ntpdate
SEE ALSO
Commands: ntpq(8), xntpd(8), xntpdc(8)
Files: ntp.conf(4)ntpdate(8)