DE

↑ ↓ select, Enter open, Esc close

Check which scripts in cron.daily actually run

harmlessCrondebian, ubuntu
Adjust the values, the command updates live
user@server
run-parts --test /etc/cron.daily

run-parts --test only lists the files that would actually be executed on the next run. On Debian, run-parts ignores all files with a dot in the name as well as non-executable files, so a script named backup.sh never runs there. If a script is missing from the output, renaming it without the extension and running chmod +x usually helps.

Note: For the other directories, use hourly, weekly or monthly as the interval.

Also searched as

  • script in cron.daily not running
  • which scripts run daily
  • test cron.daily
  • run-parts dry run

Related one-liners

All in Cron

Run all scripts in cron.daily right now

#run-parts --verbose /etc/cron.daily
cautionCron

Find out which cron job runs a command

#grep -rn "wp-cron.php" /etc/crontab /etc/cron.d /etc/cron.hourly /etc/cron.daily /etc/cron.weekly /etc/cron.monthly /var/spool/cron/crontabs 2>/dev/null
harmlessCron

Prevent overlapping cron jobs with flock

$flock -n /tmp/backup.lock /usr/local/bin/backup.sh
harmlessCron

Show currently running cron jobs

$ps -eo pid,user,etime,cmd --forest | grep -A3 '[C]RON'
harmlessCron

Show system-wide cron jobs in /etc/crontab and /etc/cron.d

$grep -vE '^\s*(#|$)' /etc/crontab /etc/cron.d/*
harmlessCron

Show the cron log: when which job ran

#journalctl -u cron --since today --no-pager
harmlessCron

Read first, then run.

The commands on myline.de act directly on servers, files and databases. A wrong path or placeholder can delete data irreversibly or make a server unreachable.

  • All commands are provided without warranty and are not tested on every system.
  • Understand what a command does before running it, and check every placeholder.
  • Make a backup first and, if possible, try it on a test system.
  • You run commands at your own risk. Liability for damages is excluded to the extent permitted by law.