Of course
Well, of the three crontab lines above, the second is the interesting one for you:
You may consider it as a boolean expression, meaning that
script2.sh will run if, and only if, script1.sh finished successfully (exit 0).
This will happen at twelve o'clock.
The first line says that script1.sh will run from 4 to 11 and from 13 to 21 every 5 minutes. The last line says that script1.sh will run every 5 minues from 12.
Regards.
Hello there!
Here is my problem. I hope I can get some help about it.
I need to know how can I get the return code of an application in the Unix shell script.
The script is like below:
PREVIOUS STATEMENT & VARIABLES
sqlplus scott/tiger @$sqldir/$sqlscript
NEXT STATEMENT (Like... (7 Replies)
Hello,
I still have problems when trying to figure out if the status of an ftp was successful. I ftp to different types (nt, vax, unix, etc...) of machines. I am trying to write a universal script that will ftp a file and then check to see if the ftp was successful. I have tried the... (12 Replies)
Hi all
below is a snippet of my perl codesystem ("scp -pq $dest_file $path");How i can i trap the return status? ie if the scp fails how can i know ? (2 Replies)
Hello friends ,
I am doing the following command, but it is not wise to all files.
for temp in `find ./CSV/ -name "*.txt"`
do
sed -n -e 'N; /*Main End/p' $temp
done
Its give me the correct output for some files , but not for all files.
I mean some files contains the... (12 Replies)
I have the question:
How return the exit code from then assign :
VAR=$(command ) for ex. VAR=$(ls ....)
VAREXIT=$?
echo $VAREXIT
VAREXIT is equal to 0 if the directory exist or not exist. WHI??
if i execute the command direct from line-command , the value of $? is different if... (1 Reply)
Hi all
I'm trying to evalute the return status of a function without much success. I've put a very basic example below to explain.
check_ok() works fine but when used within an if statement, it always returns true, whether it is true or false. I'm guessing it returns true as the function... (4 Replies)
Hi,
Need some idea on file processing, I have file like below,
Processing al sources ...
...No value found :
CHECK.
Completed comparing all sources.
Comparing schedulers...
Processing al targets ...
...No value found :
From above I need to extract the line where "No value... (4 Replies)
Hi can you explain me, what does variables $@ and $* return and how are they used, if can give me a sample example it could be helpful.
Thanks in advance,
Regards,
Abhishek S. (1 Reply)
I have a script like this:
echo "enter filername in lowercase"
read -e filername exec 2>&1
echo "type the start date in format MM/DD/YYYY"
read -e startdate exec 2>&1
echo "enter the end date in format MM/DD/YYYY"
... (2 Replies)
Discussion started by: newbie2010
2 Replies
LEARN ABOUT DEBIAN
queuedefs
queuedefs(4) File Formats queuedefs(4)NAME
queuedefs - queue description file for at, batch, and cron
SYNOPSIS
/etc/cron.d/queuedefs
DESCRIPTION
The queuedefs file describes the characteristics of the queues managed by cron(1M). Each non-comment line in this file describes one queue.
The format of the lines are as follows:
q.[njobj][nicen][nwaitw]
The fields in this line are:
q The name of the queue. a is the default queue for jobs started by at(1); b is the default queue for jobs started by batch (see
at(1)); c is the default queue for jobs run from a crontab(1) file.
njob The maximum number of jobs that can be run simultaneously in that queue; if more than njob jobs are ready to run, only the first
njob jobs will be run, and the others will be run as jobs that are currently running terminate. The default value is 100.
nice The nice(1) value to give to all jobs in that queue that are not run with a user ID of super-user. The default value is 2.
nwait The number of seconds to wait before rescheduling a job that was deferred because more than njob jobs were running in that job's
queue, or because the system-wide limit of jobs executing has been reached. The default value is 60.
Lines beginning with # are comments, and are ignored.
EXAMPLES
Example 1: A sample file.
#
#
a.4j1n
b.2j2n90w
This file specifies that the a queue, for at jobs, can have up to 4 jobs running simultaneously; those jobs will be run with a nice value
of 1. As no nwait value was given, if a job cannot be run because too many other jobs are running cron will wait 60 seconds before trying
again to run it.
The b queue, for batch(1) jobs, can have up to 2 jobs running simultaneously; those jobs will be run with a nice(1) value of 2. If a job
cannot be run because too many other jobs are running, cron(1M) will wait 90 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, and if a job cannot be run because too many other jobs
are running cron will wait 60 seconds before trying again to run it.
FILES
/etc/cron.d/queuedefs queue description file for at, batch, and cron.
SEE ALSO at(1), crontab(1), nice(1), cron(1M)SunOS 5.10 1 Mar 1994 queuedefs(4)