how to store a date into file?
and how we can access date from the file?
---------- Post updated at 06:09 AM ---------- Previous update was at 06:08 AM ----------
how we can store date in file? (1 Reply)
Hi all!!
I have a nerve-wracking concept (probably for me!!) which is not understood. My crontab entry looks this way.
33 09 22 3 * /home/myexp.sh "Bgp4 ALL" >/dev/null 2>&1
But cron gets started occasionally. Sometimes it does. Sometimes it does not. And sometimes it hangs in the middle (I... (1 Reply)
Hi,
I have written a shell script to transfer files to a SFTP server passing the filername, source and dest directory as parameters and it runs well. :)
I want to schedule this script to run periodically using a cron job.
root@pingu # cat /etc/crontab
SHELL=/bin/bash... (1 Reply)
this my source file
************* fixed ***************
Begin
equipmentId : d9
processor : fox
number : bhhhhhh
Variable # 1:
Id : 100
Type : 9
nType : s
gType : 5f
mType : 4
LField : England
DataField : london
Length ... (6 Replies)
Hi,
On linux cluster, i created a script to delete all temp files older than 5 days.
i am able to execute the script "dsh -ea script.ksh" in management node directly
But when i schedule "dsh -ea script.ksh" in crontab in management node it tells dsh command not found.
How to solve... (2 Replies)
I am new to creating crontab file , i just wrote below
(40 19 * 3 * /root/maths/practisecron.sh), the script just prints "Hi".
When ever i save the above file i am getting this .
# crontab -e
crontab: installing new crontab
Can you please check where it went wrong.. (1 Reply)
So I've been tasked with creating a shell script to run in a cron every few minutes to check duplex settings on my eth0 nic card. I would like for the server to send a wall message to whoever is on the console or in a terminal session. Below is what I have so far.
0,10,20,30,40,50 * * * * ... (1 Reply)
So I've been tasked with creating a shell script to run in a cron every few minutes to check duplex settings on my eth0 nic card. I would like for the server to send a wall message to whoever is on the console or in a terminal session. Below is what I have so far.
0,10,20,30,40,50 * * * * ... (7 Replies)
Good evening, ive got this cron to be run:
if i run this manually it doesnt work,it takes me to the prompt again
/export/app/CO/opge/scr/Informe_parametros_colombia.ksh >/dev/null 2>&1
here is the code fragment:
coopge@coopge: opge PRODUCCION>more... (1 Reply)
Hello gurus,
I am making what I think is a simple db2 call from within a shell script but I am having difficulty producing the desired
report when I run the script shown below from a shell script in cron. For example, my script and the crontab file setup
is shown below:
#!/bin/ksh
db2... (3 Replies)
Discussion started by: okonita
3 Replies
LEARN ABOUT MOJAVE
cron
CRON(8) BSD System Manager's Manual CRON(8)NAME
cron -- daemon to execute scheduled commands (Vixie Cron)
SYNOPSIS
cron [-s] [-o] [-x debugflag[,...]]
DESCRIPTION
The cron utility is launched by launchd(8) when it sees the existence of /etc/crontab or files in /usr/lib/cron/tabs. There should be no
need to start it manually. See /System/Library/LaunchDaemons/com.vix.cron.plist for details.
The cron utility searches /usr/lib/cron/tabs for crontab files which are named after accounts in /etc/passwd; crontabs found are loaded into
memory. The cron utility also searches for /etc/crontab which is in a different format (see crontab(5)).
The cron utility then wakes up every minute, examining all stored crontabs, checking each command to see if it should be run in the current
minute. When executing commands, any output is mailed to the owner of the crontab (or to the user named in the MAILTO environment variable
in the crontab, if such exists).
Additionally, cron checks each minute to see if its spool directory's modification time (or the modification time on /etc/crontab) has
changed, and if it has, cron will then examine the modification time on all crontabs and reload those which have changed. Thus cron need not
be restarted whenever a crontab file is modified. Note that the crontab(1) command updates the modification time of the spool directory
whenever it changes a crontab.
Available options:
-s Enable special handling of situations when the GMT offset of the local timezone changes, such as the switches between the standard
time and daylight saving time.
The jobs run during the GMT offset changes time as intuitively expected. If a job falls into a time interval that disappears (for
example, during the switch from standard time) to daylight saving time or is duplicated (for example, during the reverse switch),
then it is handled in one of two ways:
The first case is for the jobs that run every at hour of a time interval overlapping with the disappearing or duplicated interval.
In other words, if the job had run within one hour before the GMT offset change (and cron was not restarted nor the crontab(5)
changed after that) or would run after the change at the next hour. They work as always, skip the skipped time or run in the added
time as usual.
The second case is for the jobs that run less frequently. They are executed exactly once, they are not skipped nor executed twice
(unless cron is restarted or the user's crontab(5) is changed during such a time interval). If an interval disappears due to the GMT
offset change, such jobs are executed at the same absolute point of time as they would be in the old time zone. For example, if
exactly one hour disappears, this point would be during the next hour at the first minute that is specified for them in crontab(5).
-o Disable the special handling of situations when the GMT offset of the local timezone changes, to be compatible with the old (default)
behavior. If both options -o and -s are specified, the option specified last wins.
-x debugflag[,...]
Enable writing of debugging information to standard output. One or more of the following comma separated debugflag identifiers must
be specified:
bit currently not used
ext make the other debug flags more verbose
load be verbose when loading crontab files
misc be verbose about miscellaneous one-off events
pars be verbose about parsing individual crontab lines
proc be verbose about the state of the process, including all of its offspring
sch be verbose when iterating through the scheduling algorithms
test trace through the execution, but do not perform any actions
FILES
/usr/lib/cron/tabs Directory for personal crontab files
SEE ALSO crontab(1), launchctl(1), crontab(5), launchd.plist(5), launchd(8)AUTHORS
Paul Vixie <paul@vix.com>
BSD June 17, 2007 BSD