11-11-2009
Selective input passing, for cron with multiple interval
0,0 4,5 11 11 * /pkgs/roots/scripts/job_monitor.ksh
i have the requirement like,
for the first time(4) the script should have the input parameter as "Value1"
but the second time(5) it should have the input parameter as "Value2"
Can we achieve this using any cron options ? If yes, How..??
Otherwise what is the best approach to achieve this within the script ?
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi,
I would like to trigger a scipt on every Wednesday 12:00PM.
how can schedule this script in CRON command.
Could you please help me on this. (3 Replies)
Discussion started by: koti_rama
3 Replies
2. Shell Programming and Scripting
Hi,
In awk in can pass input to a command like this
echo "1 2" | awk '{p=$1+$2;print v}'or I can use v option to pass input to awk command
In the similar way How can I pass input to a perl command. For example :
perl -pi -e 'if ( $. == 2 ) {print "Hello\n" }' input.txtIn the above... (1 Reply)
Discussion started by: john_noble
1 Replies
3. UNIX for Dummies Questions & Answers
I am trying to search a log for a particluar pattern listing the total # of occurences in the end.
I thought using a shell script for input then calling awk to search for the paramters specified. I want the script to be usable acorss envs.
Code:
#! /usr/bin/bash
# get the variables... (5 Replies)
Discussion started by: wawa44oz
5 Replies
4. Shell Programming and Scripting
Hello,
I've got a KSH which I use to monitor processes then email me when complete. I pass the process name to the script and the update interval.
Does anyone know how I can get this to execute in the background. I can't use 'scriptname &' as it starts in the background before reading in my... (3 Replies)
Discussion started by: Grueben
3 Replies
5. Shell Programming and Scripting
55,0 5,6 * * * myScript
This cron task will execute on 5:00AM, 5:55AM, 6:00AM and 6:55AM.
Is there any possibility to make it run only in the order specified
such as 5:55AM and 6:00AM (basically only on the 2 intervals) ? (1 Reply)
Discussion started by: vikram3.r
1 Replies
6. Shell Programming and Scripting
Hi,
I have one shell script where it will copy all files to a directory which is already present,
For example :
i have directory DIRA and DIRB, and my shell script will expects user input to specify which directory should files must be copied. this shell scrip i am running every day using... (1 Reply)
Discussion started by: asak
1 Replies
7. Shell Programming and Scripting
I have a shell program that calls another shell program
the following code works
. chkTimeFormat.sh "10/9/12 17:51:19:783."|read c
but when I am passing the the time in a variable like in the code below, the shell chkTimeFormat.sh is not returning proper value
time="10/9/12... (9 Replies)
Discussion started by: swayam123
9 Replies
8. Shell Programming and Scripting
Hi All,
I have to insert 2 values to a text file in specific places. I have been able to extract each variable value via a script but am not able to send these variable values to the text file.
Pasted is the script for extracting the variable values:
for i in `ls -1` ... (2 Replies)
Discussion started by: danish0909
2 Replies
9. UNIX for Dummies Questions & Answers
May i please know why is it printing the script name for $0 when i pass those parameters to function.
#!/bin/bash -x
usage()
{
echo "In Usage Function"
echo $0
echo $1
echo $2
}
echo "printing first time"
echo $0
echo $1
echo $2
usage $0 $1 $2
Output: (2 Replies)
Discussion started by: Ariean
2 Replies
10. Shell Programming and Scripting
Dear All,
I have a question on what is the best way to control and list out multiple selective keywords to print out the report
Below is the Sample output of the listing
Code1
Code1
Code1
Identifier "Job"
Code2
Code2
Code2
Name "Impressive"
Code3
Code3
Code3
AGT_Manual
Code1... (3 Replies)
Discussion started by: ckwan
3 Replies
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