08-16-2010
You can try this
*/45 * * * * script_name
here */45 in minutes fields indicates in every 45 minutes.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hello,
I would like setup a CRON job to rename my server's name (host name) every day. For some reason it changes its own name every couple days to server-2.local fron server.local.
Thank you!
-Chris (3 Replies)
Discussion started by: christo16
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. Solaris
Hi I am new to solaris zones...........
I created a zone in solaris and i am trying to add a cron entry to that by
crontab -e but when I enter that command it is just showing 253 number.....
But when I enter crontab -l there are some entries my question is how to add cron entry??
when... (3 Replies)
Discussion started by: vijaysachin
3 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. UNIX for Dummies Questions & Answers
Hi guys,
How can I specify the start and end time of a cron job. And my start time and end time are specified by minutes. For example, I want to set up a cron runs every 3 minutes from 18:40 to midnight. How can i do this please? Many thanks
Best regards,
Clu (4 Replies)
Discussion started by: clu
4 Replies
6. Shell Programming and Scripting
HI I am new to unix .
I wanted to create a cron job that runs a script every 10 min .So when I enter
vi /etc/crontab
I get the following output
SHELL=/bin/bash
PATH=/sbin:/bin:/usr/sbin:/usr/bin
MAILTO=root
HOME=/
# run-parts
01 * * * * root run-parts /etc/cron.hourly
02 4 * *... (1 Reply)
Discussion started by: ptappeta
1 Replies
7. 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
8. Shell Programming and Scripting
Hello Gurus,
I have a requirement to run a job from cron only for 30 minutes duration daily twice at 8.35 am and 20.35 pm
Can you please suggest how to schedule the job?
Thanks-
Pokhraj (5 Replies)
Discussion started by: pokhraj_d
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 HPUX
queuedefs
queuedefs(4) Kernel Interfaces Manual queuedefs(4)
NAME
queuedefs - queue description file for at, batch, and crontab
SYNOPSIS
DESCRIPTION
The file describes the characteristics of the queues managed by (see cron(1M)). Each non-comment line in this file describes one queue.
The format of the lines are as follows:
[njob[nice[nwait
The fields in this line are:
q The name of the queue, such that is the default queue for jobs started by (see at(1)), is the queue for jobs started by
(see at(1)), and is the queue for jobs run from a file (see crontab(1)). Queue names through designate user-defined
queues.
njob The maximum number of jobs that can be run simultaneously in that queue. Although any number can be specified here, (see
cron(1M)) by default limits the number of jobs that can be run on all the queues to 100. This limitation can be removed
by setting the variable to 1 in the file.
nice The value to give to all jobs in that queue that are not run with a user ID of super-user (see nice(1)). 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 more than 100 jobs were running in all the queues (see njob above).
EXAMPLES
Consider the following file:
The file is interpreted as follows:
The queue, for jobs (see at(1)), can have up to 4 jobs running simultaneously, and those jobs will be run with a value of
1.
Since no nwait value is given, if a job cannot be run because too many other jobs are running, will wait 60 seconds
before trying again to run it (see cron(1M)).
The queue, for jobs (see at(1)), can have up to 2 jobs running simultaneously. Those jobs will be run with a value of 2.
If a job cannot be run because too many other jobs are running, 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 value of 2, and if a job cannot be run because
too many other jobs are running, will wait 60 seconds before trying again to run it.
SEE ALSO
at(1), nice(1), crontab(1), cron(1M), proto(4).
STANDARDS CONFORMANCE
queuedefs(4)