01-16-2001
Then use a wrapper.
Create another script like launch.scr1;
#!/bin/sh
touch /tmp/scr1.lock
/path/to/SCR1
wait
rm -f /tmp/scr1.lock
------------------
And then create the wrapper for SCR2 called launch.scr2
#!/bin/sh
if [ -e /tmp/scr1.lock ]
then exit
else /path/to/SCR2
fi
------------------
Than change your cron entries to execute the wrapper scripts instead of the actual scripts/executables.
[Edited by 98_1LE on 01-16-2001 at 10:13 AM]
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
what command can i use to tell if a script is running under different users? (1 Reply)
Discussion started by: csnewbie
1 Replies
2. Shell Programming and Scripting
Hi,
Iam having the scripts as follows. i jus want to run those in parallel.
main aim is to minimise the time for overall execution of the script.
now out.txt is having 1 lac records.
script1(split.sh)
split -1000 out.txt splitout
ls -A splitout* > filelist.txt
cat filelist.txt... (6 Replies)
Discussion started by: nivas
6 Replies
3. Shell Programming and Scripting
Hi All,
My input file name is 1.sh
the contents of file are
cat status2.txt | while read filename
do
echo "$filename"
echo "first content of the file is ${filename}"
echo "second content of the file is ${filename}"
echo "second content of the file is ${filename}"
if } -eq 0 -a... (1 Reply)
Discussion started by: sunitachoudhury
1 Replies
4. Shell Programming and Scripting
Hello everybody,
I'm trying to run a shell script in crontab file. But anyhow it's not getting executed. Following is the command that I've used in crontab.
30 07 * * * . ./.cronprofile;/om/reports/reportscripts/jitu/prod/prd_pre_to_post.sh
35 11 * * * .... (3 Replies)
Discussion started by: jitu.jk
3 Replies
5. UNIX for Dummies Questions & Answers
I am checking one until loop with the following logic
until ||
||||
do
sleep 30
done
before running this i am exporting above variables to SUCCESS.But the loop is running in infinite loop.My requirement is to make the loop run until
all the 3 variables are SUCCESS or any of the 3... (2 Replies)
Discussion started by: dr46014
2 Replies
6. Shell Programming and Scripting
Hi All,
Am using the below command to start my application using the root user
su - bin -c "/home/bin/test/start.sh"
but am getting the error becaue i have set some environment varibales in bin .profile
when i execute the command start.sh by logging directly into bin account it's... (8 Replies)
Discussion started by: ravi.sri24
8 Replies
7. Shell Programming and Scripting
Hi all,
I have set up a cron job which calls another shell script shell script which in turn calls a Java process. The cron tab looks so.
0,30 7-18 * * 1-5 /u01/home/weblogic/brp/bin/checkstatus.sh >> /u01/home/weblogic/logs/checkstatus.log
The checkstatus.sh scripts looks like this.
... (4 Replies)
Discussion started by: sirbrian
4 Replies
8. Solaris
I need to run a script (from cron) that runs a second script.
What worries me is that second script, when run from bash, upon finishing doesn't return to bash unless I press the 'Enter' key.
I presume that's because last command in that script ends with &
Could that be a problem for cron?... (2 Replies)
Discussion started by: orange47
2 Replies
9. UNIX for Dummies Questions & Answers
Hi,
I need a script (ksh) on ServerAdmin that will run an archive scripts from different several Servers through ssh. The problem is that how can i switch user when before running the archive script. I already configured password-less connection on the servers.
server 1... (1 Reply)
Discussion started by: chococrunch6
1 Replies
10. Shell Programming and Scripting
I have an if condition. If that condition is true then one script will be run and after that I need to check another condition based on the output value of first script.
i tried like below :
cd lock
if ; then
rm exitup
if ; then
kb_shutdown
kb_startup
if ; then
rm exitup
if ;... (3 Replies)
Discussion started by: charanarjun
3 Replies
LEARN ABOUT OSF1
queuedefs
queuedefs(4) Kernel Interfaces Manual queuedefs(4)
NAME
queuedefs - Queue description file for at, batch, and cron commands
DESCRIPTION
The queuedefs file describes the characteristics of the queues managed by cron or specifies other characteristics for cron. Each noncom-
ment line in this file describes either one queue or a cron characteristic. Each uncommented line should be in one of the following for-
mats.
q.[njobj][nicen][nwaitw] max_jobs=mjobs log=lcode
The fields in these lines are as follows: The name of the queue. Defined queues are as follows: The default queue for jobs started by at
The default queue for jobs started by batch The default queue for jobs run from a crontab file
Queues d to z are also available for local use. The maximum number of jobs that can be run simultaneously in the queue; if more
than njob jobs are ready to run, only the first njob jobs will be run. The others will be initiated as currently running jobs ter-
minate. The nice(1) value to give to all jobs in the queue that are not run with a user ID of superuser. The number of seconds to
wait before rescheduling a job that was deferred because more than njob jobs were running in that queue, or because the system-wide
limit of jobs executing (max_jobs) has been reached. The maximum number of active jobs from all queues that may run at any one
time. The default is 25 jobs. Logging level of messages sent to a log file. The default is 4. Defined levels are as follows:
level-code level
0 None
1 Low
2 Medium
3 High
4 Full
Lines beginning with # are comments, and are ignored.
EXAMPLES
The following file specifies that the b queue, for batch jobs, can have up to 50 jobs running simultaneously; that those jobs will be run
with a nice value of 20. If a job cannot be run because too many other jobs are running, cron will wait 60 seconds before trying again to
run it. All other queues can have up to 100 jobs running simultaneously; they will be run with a nice value of 2. If a job cannot be run
because too many other jobs are running cron will wait 60 seconds before trying again to run it. b.50j20n60w
The following file specifies that a total of 25 active jobs will be allowed by cron over all the queues at any one time, and cron will log
all messages to the log file. The last two lines are comments that are ignored. max_jobs=25 log=4 # This is a comment # And so is this
FILES
Main cron directory The default location for the queue description file.
RELATED INFORMATION
Commands: at(1), cron(8), crontab(1), nice(1)
delim off
queuedefs(4)