06-29-2017
I assume you want to run your script from crontab.
You can store the current job name in a file.
Before you do it, compare it with the old file contents; if different then send mail.
This User Gave Thanks to MadeInGermany For This Post:
5 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi,
Thanks in advance.
i need to kill a unix background running job after that job process completes.
i can kill a job by giving the following unix command
kill -9 processid
how to kill the job after the current process run gets completed ?
Appreciate your valuable help.
... (1 Reply)
Discussion started by: dtazv
1 Replies
2. UNIX for Dummies Questions & Answers
Just spent the last hour cruising the FAQ and doing some searches. I learn best by getting one or two books and just starting from scratch and building up a system. Looks like that's the way most of you recommend getting going anyway. I'm armed with several book titles now, and I'll head off to... (2 Replies)
Discussion started by: Rowan
2 Replies
3. UNIX for Dummies Questions & Answers
Hi,
I have multiple functions that can be called by any shell script. These functions have inbuilt echo statements to logs their activity into a log file. When I run multiple shell scripts that call these functions, they all log into the same log file and I am not able to differentiate which... (2 Replies)
Discussion started by: new_learner
2 Replies
4. Shell Programming and Scripting
I would like to know the maximum integer that a variable can hold. Actually one of my variable holds value 2231599773 and hence the script fails to process it.Do we have any other data type or options available to handle this long integers? (9 Replies)
Discussion started by: michaelrozar17
9 Replies
5. Shell Programming and Scripting
Hi..
I need to put multiple jobs on ON HOLD in Autosys.. please help me on this.
For Example:
1)ABCD_EFGH_IJKL
2)abcd_efgh_ijkl (2 Replies)
Discussion started by: Maanjesh
2 Replies
LEARN ABOUT FREEBSD
atrun
ATRUN(8) BSD System Manager's Manual ATRUN(8)
NAME
atrun -- run jobs queued for later execution
SYNOPSIS
atrun [-l load_avg] [-d]
DESCRIPTION
Atrun runs jobs queued by at(1).
Root's crontab(5) file /etc/crontab has to contain the line
*/5 * * * * root /usr/libexec/atrun
so that atrun gets invoked every five minutes.
At every invocation, atrun will start all the jobs in the lowercase queues whose start time has elapsed. In addition, if the load average
over the last minute was less than the specified limit then a maximum of one batch job (denoted by the uppercase queues) is started.
Before starting a job, atrun will check the status of its owner's account with pam(3) and refuse to run the job if the account is unavail-
able, e.g., locked out or expired.
OPTIONS
-l load_avg
Specify a limiting load factor, over which batch jobs should not be run, instead of the default of 1.5 * number of active CPUs.
-d Debug; print error messages to standard error instead of using syslog(3).
WARNINGS
For atrun to work, you have to start up a cron(8) daemon.
FILES
/etc/pam.d/atrun pam.conf(5) configuration file for atrun
/var/at/jobs Directory containing job files
/var/at/spool Directory containing output spool files
SEE ALSO
at(1), crontab(1), pam(3), syslog(3), crontab(5), pam.conf(5), cron(8)
BUGS
The functionality of atrun should be merged into cron(8).
BSD
October 30, 2012 BSD