08-25-2008
I dont believe this syntax to work in HPUX (I wonder on what it does though...)
but you can also let a script to run every day using cron, and in this script, test if ist a 6th day and if so run your job...
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi,
I am trying to schedule a job in linux through the crontab command.My script actually does some text processing and echoes some output.My cron scheduler is working fine,but the output messages(echoes from script) is mailed to my mail account(in unix -/var/local/mail).Is it not possible... (0 Replies)
Discussion started by: DILEEP410
0 Replies
2. UNIX for Advanced & Expert Users
I have created two scripts to call SQL scripts to do some work. The scripts was successfully executed many times by manual. When I scheduled two scripts in crontab, I gave all necessary parameters. It could start, but couldn't run through. The log file didn't give enough error info. Anyone can help... (10 Replies)
Discussion started by: duke0001
10 Replies
3. UNIX for Advanced & Expert Users
Hi,
we reboot our Linux server yesterday and since then (specialy last night) no job from crontab has run. Any idea ? What should I look for to investigate?
Many thanks. (5 Replies)
Discussion started by: big123456
5 Replies
4. Solaris
Hi experts,
I want to set the crontab for my script which will run every 20 seconds
I think below could be the possible one-
*/3 * * * * /export/home/username/scripts/runing.sh
As my system(SOLARIS 9) is live- i am confused to implement before make sure !!!
I need... (4 Replies)
Discussion started by: thepurple
4 Replies
5. Shell Programming and Scripting
Hello,
I have to schedule a command to run on every 3 days. Whether the below cron entry will work?
0 3 */3 * * command
Please help me out and thanks in advance! (6 Replies)
Discussion started by: Arunprasad
6 Replies
6. Shell Programming and Scripting
Hi,
please advise a script, something like this:
If ;
then
do something
else ( or for any other day of the week )
do otherthing
fi
Thanks (5 Replies)
Discussion started by: fed.linuxgossip
5 Replies
7. Shell Programming and Scripting
Hi,
I have a script which checks to see if an app is running and will restart it if it is not.
For some reason when I run it from the crontab it always says it is not running.
The script is as follows: -
#!/bin/sh
#
# The following script will look for the PID of SickBeard and output... (15 Replies)
Discussion started by: simpic
15 Replies
8. Shell Programming and Scripting
Hello all,
I'm trying to write a script to gather and send data and it works just fine at the bash command line, but when executing from CRON, it does not run properly.
My scripting skills are pretty limited and there's probably a better way, but as I said it works at the command line, but... (12 Replies)
Discussion started by: rusman
12 Replies
9. Shell Programming and Scripting
Can someone please help me on how to schedule script to run every 45 days in crontab ?
Thanks,
Prince (5 Replies)
Discussion started by: prince1987
5 Replies
10. Shell Programming and Scripting
I'm trying to get a crontab to run, every Friday at 11am and the problem is that it isn't running at all.
0 11 * * 6 /Users/martinb/Documents/SYSADMIN/Regular-Scripts/Info-And-Backups.sh
Here's a link to a screenshot of my script (I've censored my email address).
Screen Shot 2017 11 03... (3 Replies)
Discussion started by: $shell_Learner
3 Replies
LEARN ABOUT OPENSOLARIS
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.11 1 Mar 1994 queuedefs(4)