12-18-2015
Hi RudiC,
Quote:
You can either have the job terminate itself using e.g. a timer/counter
Can you please suggest as how to terminate the job itself by using counter/timer?
Thanks-
Pokhraj Das
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
I have the below crontab job that it will run at every 7:00am - 10:00am , it work fine , now if I want to skip to run the crontab job at a specific time , eg. I want the script not to run at next Monday 8:00am ( only skip this time , other time is normal ) , how can I make it ? is it possible ?... (3 Replies)
Discussion started by: ust
3 Replies
2. Shell Programming and Scripting
I have a perl script, when I ran manually it works perfect. I check the permissions which are fine.
How can I find out why it is not running? how can I setup a log to check.
I am running it on solaris 9.
It compares multiple files, SCP and then send out an e-mail.
As I said when I ran it... (2 Replies)
Discussion started by: amir07
2 Replies
3. UNIX for Advanced & Expert Users
Hi, new to this forum and not sure if this is the right place to post. I'm new to cron jobs and scripts, and I need some help with a script to be used with a cron job. I already have a bot set up at a certain website address and need a script that the cron job will load every day that tells it to... (1 Reply)
Discussion started by: klawless
1 Replies
4. Shell Programming and Scripting
Hi
I need to run a script every five minutes and it should run between 07-15 hours all days.
How i can achieve this...
i tried like this
*/5 07-15 * * * /scripts/CreateFtpData.sh
It throws an error... (1 Reply)
Discussion started by: aemunathan
1 Replies
5. Solaris
How to setup a cron job to run every 45 minutes in Solaris 5.10 (9 Replies)
Discussion started by: reyazan
9 Replies
6. UNIX for Advanced & Expert Users
my colleague was asking about this:
is there a way to run a cron job biweekly, like a script five.sh
to run every *OTHER* Friday within November
its part about every other Friday we cant find any documentation.
thx
L (8 Replies)
Discussion started by: lydiaflamp
8 Replies
7. Shell Programming and Scripting
Hi,
First of all merry christmas and Happy holidays to all :D
My situation is as below,
When a backup job runs on a mainframe server, it creates a 0byte file on a network drive which is accessible through linux
Linux server : Red Hat Enterprise Linux Server release 5.3 Beta (Tikanga)
File... (6 Replies)
Discussion started by: sam05121988
6 Replies
8. Shell Programming and Scripting
Hi,
1)
If some job supposed to run on 1st of every month at 7 AM
In cron job when we have a blackout on the 1st ( i.e when 1st falls on a sunday ) how can we make the job run the next business day?
2) How can we run a job on 25th of every quarter 7 AM(jan,apr,jul,oct)
And if 25th... (5 Replies)
Discussion started by: System Admin 77
5 Replies
9. Shell Programming and Scripting
Hello Gurus,
I want to schedule a cron job which will run every 2 minutes starts at 11:25 AM and 3:25 AM daily.
Can you please suggest as how to schedule the job.
Thanks-
Pokhraj Das (2 Replies)
Discussion started by: pokhraj_d
2 Replies
10. Shell Programming and Scripting
Hi,
I created this cron job for asterisk to send sms daily to a number
#!/bin/sh
#custom mod - send sms once a day, at 07:00.
CRON_PATH="/etc/asterisk/gw/crontabs_root";
if ! grep 'gsm send sms' $CRON_PATH > /dev/null 2>&1 ;then
echo "* 7 * * * asterisk -rx 'gsm send sms 1 7666... (4 Replies)
Discussion started by: jazzyzha
4 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