Limiting Cron Job Frequency with a Bash Script

A cron job that runs every minute can use more CPU and memory than the work it does is worth, and on a busy server many such jobs add up. There are two ways to limit this: a server administrator can enforce a minimum interval for every user's cron jobs, and anyone can make a single job skip runs that come too soon or overlap. This guide shows both with safe bash scripts, and explains what already applies on Domain India shared hosting.

1. Why limit cron frequency

Each cron run starts a new process: often a PHP interpreter, a database connection and your application's start-up code. At every minute, that is 1,440 starts a day per job. Two problems follow:

• Load adds up. On a server with many accounts, hundreds of every-minute jobs start at the same second and cause a spike.
• Runs pile up. If a job takes longer than its interval, the next copy starts before the last one finishes, and several copies compete for the same resources.

Most tasks, such as sending queued mail, clearing caches or running WordPress's scheduled events, work fine every 5 or 15 minutes.

2. What applies on Domain India shared hosting

We checked our servers on 24 September 2026. On our cPanel and DirectAdmin shared servers, an hourly system job looks for user cron jobs scheduled every minute (* * * * *) or every 2 or 3 minutes (*/2 or */3 with the other fields set to *) and changes them to every 4 minutes (*/4 * * * *). In practice:

Webuzo was not checked. You can't change this rule on shared hosting, and it covers the whole server. Applications that expect a job every minute, such as Laravel's scheduler, will run it every 4 minutes, so check that your tasks tolerate that. To set up jobs in your control panel, see how to set up a cron job and cron job commands.

Cron jobs also count against your account's CPU, memory and process limits; see understanding hosting resource limits.

3. For a single job: skip runs that come too soon

The simplest and safest way to limit one job is to wrap it. This script runs your command only if no other copy is running and the last successful run was at least a set number of minutes ago:

#!/bin/bash
# cron-guard.sh MIN_MINUTES NAME COMMAND...
# Example: cron-guard.sh 15 sitemap /usr/local/bin/php /home/user/cron/sitemap.php
set -u
min_minutes="$1"; name="$2"; shift 2

state_dir="$HOME/.cron-guard"
mkdir -p "$state_dir"
lock="$state_dir/$name.lock"
stamp="$state_dir/$name.last"

exec 9>"$lock"
flock -n 9 || exit 0                      # another copy is still running

if [ -f "$stamp" ]; then
  last=$(cat "$stamp")
  now=$(date +%s)
  if [ $(( now - last )) -lt $(( min_minutes * 60 )) ]; then
    exit 0                                # too soon since the last run
  fi
fi

"$@" && date +%s > "$stamp"

Save it in your home folder (for example ~/bin/cron-guard.sh), make it executable with chmod 700 ~/bin/cron-guard.sh, and call it from cron:

*/5 * * * * /home/USERNAME/bin/cron-guard.sh 15 sitemap /usr/local/bin/php /home/USERNAME/cron/sitemap.php >/dev/null 2>&1

Cron checks every 5 minutes, but the task runs at most every 15 minutes and never twice at once. The timestamp is written only after a successful run, so a failed run is retried at the next check. If you only need to stop overlaps, flock on its own is enough: /usr/bin/flock -n /home/USERNAME/cron.lock COMMAND.

4. For a server you run: enforce a minimum interval for all users

On your own VPS or server with several users, you may want a server-wide rule like ours. This applies to servers where you have root; on shared hosting you can't do it. A safer version of the classic script:

#!/bin/bash
# /usr/local/sbin/cron-min-interval.sh, run hourly by root
MIN=5                                   # minimum minutes between runs
LOG=/var/log/cron-min-interval.log

# cronie (AlmaLinux, Rocky) uses /var/spool/cron; Debian and Ubuntu use /var/spool/cron/crontabs
SPOOL=/var/spool/cron
[ -d /var/spool/cron/crontabs ] && SPOOL=/var/spool/cron/crontabs

exec 9>/run/cron-min-interval.lock
flock -n 9 || exit 0

too_often="^(\*|\*/[1-$((MIN - 1))])( \* \* \* \*)"
for tab in "$SPOOL"/*; do
  [ -f "$tab" ] || continue
  user=$(basename "$tab")
  [ "$user" = root ] && continue
  if grep -qE "$too_often" "$tab"; then
    cp -p "$tab" "/root/crontab-backup-$user-$(date +%F)"
    sed -i -E "s#$too_often#*/$MIN\2#" "$tab"
    echo "$(date '+%F %T') $user: changed to every $MIN minutes" >> "$LOG"
  fi
done

Run it from root's crontab with 0 * * * * /usr/local/sbin/cron-min-interval.sh. Compared with older scripts that do the same job, this version:

• uses one pattern instead of a loop that rewrites the file many times, and works for any minimum from 2 to 10 minutes;
• skips root, so system jobs are never changed;
• backs up each crontab before editing it and logs every change;
• uses a lock, so two copies never edit the same file at once;
• finds the right spool folder on both RHEL-family and Debian-family systems.

It only catches the simple every-N-minutes forms. A schedule such as */2 9-18 * * * or a list of minutes passes unchanged, so treat it as a guard rail, not a complete control.

5. Alternatives worth knowing

• systemd timers on your own server can add a random delay (RandomizedDelaySec) so jobs don't all start at the same second, and they never start a second copy of a unit that is still running.
• A queue worker is better than an every-minute cron for work that arrives continuously. On shared hosting a permanent worker isn't possible; the App Platform or a VPS can run one.
• cron.allow and cron.deny in /etc control which users may use cron at all.

For more on scheduling system tasks, see automating maintenance with cron and anacron.

6. Where Domain India fits

Cron jobs are part of every Domain India cPanel, DirectAdmin and Webuzo shared hosting plan, set up from the control panel. If your application genuinely needs a task every minute or a process that runs all the time, a VPS gives you root access and your own cron and systemd. The cards show Domain India list prices on 19 September 2026, excluding 18% GST.

Frequently asked questions

Ready to schedule your jobs? Set them up with how to set up a cron job, compare VPS plans if you need per-minute tasks, or open a support ticket if a job doesn't run.