Some cron servers also accept this syntax:-
This is the step from the zero of that item, so should be a factor of the maximum, e.g. 2, 3, 4, 6 or 12 for the hours. I can't see a neat way to do it every 10 minutes replacing 5,15,25,35,45,55, although you could build it something like this:-
The best place to check if your host supports it is the manual page for the file crontab.
Often this can be found with man 5 crontab but check with man -k crontab to get the various options for pages you can read, such as Unix.com man page for crontab file
I hope that this helps,
Robin
Last edited by rbatte1; 12-21-2016 at 09:05 AM..
Reason: Smartened URL display
I want to add these no. these are in the format of
days:hours:minutes:sec
I want result in this format only
0:00:04:59
0:00:00:12
0:00:00:28
0:00:00:03
0:01:29:35
0:00:00:19
0:01:05:21
Is any body ca help me?????
To get This..
Thanks
Nishant (1 Reply)
hi guys!
I have problem with cron :rolleyes:
2,4,6,8,10,12,14,18,20,22,24,26,28,30,32,34,36,38,40,42,44,46,48,50,52,54,56,58,60 * * * * /usr/local/george/update.py
I try this to schedule the script to run every second min forever :cool: but it doesn't work :o
any idea?
thanks in... (4 Replies)
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)
Hello All,
Anybody please help me to know ,what happens when a user having entry in both cron.allow and cron.deny files.Wheather the user will be able to access the crontab???
Thanks in advance
Vaisakh (5 Replies)
stupid question im sure, but its frustrating
My cron jobs are off by 5 hours. My system time is right but all of my cron jobs are running approximately 5 hours late. Any idea why? (4 Replies)
Hi All
I have a problem, I wonder if you can help me sort it out:
I have the following entry in the cron:
00 1,13 * * * /home/report/opn_amt_gestores_credito.ksh > opn_amt_gestores_credito.log
But the entry only runs at 01:07
I have stopped the cron deamon, and started, but it still... (39 Replies)
Hi
Is there any way to disable cron adhoc ?
I want to run a script for every one minute between 04 to 00 hours
will the below serves my purpose ?
01 04-00 * * * <your script> (1 Reply)
Hi,
I am trying to run a script in cron every 5 min in SOLARIS 10
When I do5 * * * * /path to fileor*/5 * * * * /path to file
Doesn't work. Please let me know what should I put in the cron entry
Thanks (2 Replies)
I have unix epoch time 1441678454803, Can you please help me to print this time in below format ?
DAY,HOUR,MIN,SEC
Appreciate your help!!!
Thanks,
Prince (7 Replies)
Discussion started by: prince1987
7 Replies
LEARN ABOUT XFREE86
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)