How to setup CRON job to run every 10 seconds in Linux?
To elaborate on Sougata Bose's answer, I think the OP wants a command to be run every 10 seconds from a start time; not 10 seconds after the first minute and every subsequent minute.
cron only has a resolution of 1 minute (there are other tools I think that may have finer resolutions but they are not standard on unix).
Therefore, to resolve your issue you need 60 seconds / 10 seconds = 6 cron jobs, each with a sleep.
e.g. run crontab -e and add the following lines to your chosen editor:
* * * * * ( /usr/bin/wget http://api.us/application/ )
* * * * * ( sleep 10 ; /usr/bin/wget http://api.us/application/ )
* * * * * ( sleep 20 ; /usr/bin/wget http://api.us/application/ )
* * * * * ( sleep 30 ; /usr/bin/wget http://api.us/application/ )
* * * * * ( sleep 40 ; /usr/bin/wget http://api.us/application/ )
* * * * * ( sleep 50 ; /usr/bin/wget http://api.us/application/ )
Run Cron job every N minutes plus offset
To run a task every 20 minutes starting at 5 past the hour, try this:
5-59/20 * * * *
Explanation
An *
in the minute field is the same as 0-59/1
where 0-59
is the range and 1
is the step. The command will run at the first minute in the range (0), then at all successive minutes that are distant from the first by step (1), until the last (59).
Which is why */20 * * * *
will run at 0 minutes, 20 minutes after, and 40 minutes after -- which is the same as every 20 minutes. However, */25 * * * *
will run at 0 minutes, 25 minutes after, and 50 minutes after -- which is not the same as every 25 minutes. That's why it's usually desirable to use a step value in the minute field that divides evenly into 60.
So to offset the start time, specify the range explicitly and set the first value to the amount of the offset.
Examples
5-59/20 * * * *
will run at 5 minutes after, 25 minutes after, and 45 minutes after.
10-59/25 * * * *
will run at 10 minutes after and 35 minutes after.
1-59/2 * * * *
will run every odd minute.
execute crontab twice daily at 00h and 13:30
You can't do what you want in one entry, since the two minute definitions will apply for both hour definitions (as you've identified).
The solution is (unfortunately) use two cron entries. One for 00:00 and one for 13:30.
An alternative is perhaps to execute one script at 00:00. That script would execute your original script, then wait 13.5 hours and then execute that script again. It would be easy to do via a simple sleep command, but I think it's unintuitive, and I'm not sure how cron
manages such long running processes (what happens if you edit the crontab
- does it kill a spawned job etc.)
Running a cron every 30 seconds
You have */30
in the minutes specifier - that means every minute but with a step of 30 (in other words, every half hour). Since cron
does not go down to sub-minute resolutions, you will need to find another way.
One possibility, though it's a bit of a kludge(a), is to have two jobs, one offset by 30 seconds:
# Need these to run on 30-sec boundaries, keep commands in sync.
* * * * * /path/to/executable param1 param2
* * * * * ( sleep 30 ; /path/to/executable param1 param2 )
You'll see I've added comments and formatted to ensure it's easy to keep them synchronised.
Both cron
jobs actually run every minute but the latter one will wait half a minute before executing the "meat" of the job, /path/to/executable
.
For other (non-cron
-based) options, see the other answers here, particularly the ones mentioning fcron
and systemd
. These are probably preferable assuming your system has the ability to use them (such as installing fcron
or having a distro with systemd
in it).
If you don't want to use the kludgy solution, you can use a loop-based solution with a small modification. You'll still have to manage keeping your process running in some form but, once that's sorted, the following script should work:
#!/bin/env bash
# Debug code to start on minute boundary and to
# gradually increase maximum payload duration to
# see what happens when the payload exceeds 30 seconds.
((maxtime = 20))
while [[ "$(date +%S)" != "00" ]]; do true; done
while true; do
# Start a background timer BEFORE the payload runs.
sleep 30 &
# Execute the payload, some random duration up to the limit.
# Extra blank line if excess payload.
((delay = RANDOM % maxtime + 1))
((maxtime += 1))
echo "$(date) Sleeping for ${delay} seconds (max ${maxtime})."
[[ ${delay} -gt 30 ]] && echo
sleep ${delay}
# Wait for timer to finish before next cycle.
wait
done
The trick is to use a sleep 30
but to start it in the background before your payload runs. Then, after the payload is finished, just wait for the background sleep
to finish.
If the payload takes n
seconds (where n <= 30
), the wait after the payload will then be 30 - n
seconds. If it takes more than 30 seconds, then the next cycle will be delayed until the payload is finished, but no longer.
You'll see that I have debug code in there to start on a one-minute boundary to make the output initially easier to follow. I also gradually increase the maximum payload time so you'll eventually see the payload exceed the 30-second cycle time (an extra blank line is output so the effect is obvious).
A sample run follows (where cycles normally start 30 seconds after the previous cycle):
Tue May 26 20:56:00 AWST 2020 Sleeping for 9 seconds (max 21).
Tue May 26 20:56:30 AWST 2020 Sleeping for 19 seconds (max 22).
Tue May 26 20:57:00 AWST 2020 Sleeping for 9 seconds (max 23).
Tue May 26 20:57:30 AWST 2020 Sleeping for 7 seconds (max 24).
Tue May 26 20:58:00 AWST 2020 Sleeping for 2 seconds (max 25).
Tue May 26 20:58:30 AWST 2020 Sleeping for 8 seconds (max 26).
Tue May 26 20:59:00 AWST 2020 Sleeping for 20 seconds (max 27).
Tue May 26 20:59:30 AWST 2020 Sleeping for 25 seconds (max 28).
Tue May 26 21:00:00 AWST 2020 Sleeping for 5 seconds (max 29).
Tue May 26 21:00:30 AWST 2020 Sleeping for 6 seconds (max 30).
Tue May 26 21:01:00 AWST 2020 Sleeping for 27 seconds (max 31).
Tue May 26 21:01:30 AWST 2020 Sleeping for 25 seconds (max 32).
Tue May 26 21:02:00 AWST 2020 Sleeping for 15 seconds (max 33).
Tue May 26 21:02:30 AWST 2020 Sleeping for 10 seconds (max 34).
Tue May 26 21:03:00 AWST 2020 Sleeping for 5 seconds (max 35).
Tue May 26 21:03:30 AWST 2020 Sleeping for 35 seconds (max 36).
Tue May 26 21:04:05 AWST 2020 Sleeping for 2 seconds (max 37).
Tue May 26 21:04:35 AWST 2020 Sleeping for 20 seconds (max 38).
Tue May 26 21:05:05 AWST 2020 Sleeping for 22 seconds (max 39).
Tue May 26 21:05:35 AWST 2020 Sleeping for 18 seconds (max 40).
Tue May 26 21:06:05 AWST 2020 Sleeping for 33 seconds (max 41).
Tue May 26 21:06:38 AWST 2020 Sleeping for 31 seconds (max 42).
Tue May 26 21:07:09 AWST 2020 Sleeping for 6 seconds (max 43).
If you want to avoid the kludgy solution, this is probably better. You'll still need a cron
job (or equivalent) to periodically detect if this script is running and, if not, start it. But the script itself then handles the timing.
(a) Some of my workmates would say that kludges are my specialty :-)
How would I get a cron job to run every 30 minutes?
Do:
0,30 * * * * your_command
Quartz Cron Expression: Run Job Every 10 minutes starting NOW (immediately)
check the minute your at now and add them as a list to your crontrigger. if you start the trigger at minute 12 for example add
0 2,12,22,32,42,52 * * * ?
as your cron expression
Edit:
Another solution would be to define a simpletrigger that repeats every ten minutes
SimpleTrigger trigger = new SimpleTrigger("myTrigger",
null,
new Date(),
null,
SimpleTrigger.REPEAT_INDEFINITELY,
10L * 60L * 1000L);
How to run a cronjob every X minutes?
In a crontab
file, the fields are:
- minute of the hour.
- hour of the day.
- day of the month.
- month of the year.
- day of the week.
So:
10 * * * * blah
means execute blah
at 10 minutes past every hour.
If you want every five minutes, use either:
*/5 * * * * blah
meaning every minute but only every fifth one, or:
0,5,10,15,20,25,30,35,40,45,50,55 * * * * blah
for older cron
executables that don't understand the */x
notation.
If it still seems to be not working after that, change the command to something like:
date >>/tmp/debug_cron_pax.txt
and monitor that file to ensure something's being written every five minutes. If so, there's something wrong with your PHP scripts. If not, there's something wrong with your cron
daemon.
Related Topics
How to Set a Dynamic Variable in Haproxy
Is There a Simple Way to Batch Rename Symlink Targets
Redirecting Console Output to a File in Unix
Ksh Storing Result of a Command to a Variable
Where Did Wireshark/Tcpdump/Libpcap Intercept Packet Inside Linux Kernel
Can the Sys_Execve() System Call in the Linux Kernel Receive Both Absolute or Relative Paths
Prepend to Visual Block Not Working in Vim
Best Approach to Detecting a Move or Rename to a File in Linux
How to Search for Invisible Control Characters
How to Use Find -Exec in Cmake Execute_Process
How to Set Emacsclient Background as Emacs Background
How to Build an If Condition in Shell to Check Whether Curl Succeeded
Comparing Numbers in Bash Scripting
Is There a Subversion Web Client That I Can Use
How to Install an Older Version of PHP Using Apt-Get
How to Catch Stdout Stream in Ffmpeg Then Pipe It to V4L2Loopback