Find System Cron Files Fast

System cron jobs can live in /etc/cron.d and periodic directories, so checking only crontab -l misses them.

Command

find /etc/cron.d /etc/cron.hourly /etc/cron.daily /etc/cron.weekly /etc/cron.monthly -maxdepth 1 -type f -print 2>/dev/null | sort

Before you run this

System impact: Read-only. Can create load on large logs, directories, filesystems, or process tables.

When not to use it: Do not assume every listed file is executable or valid under run-parts naming rules.

Expected output

System cron file paths under /etc/cron.d and periodic cron directories. Empty output means this host may not use those locations or permissions hide them.

System impact

Read-only, can be slow. Nothing changes. The command lists system cron files in stable order.

May require elevated permissions on protected paths or service-owned files.

Scope this to the smallest useful path or service on busy systems.

Recovery / rollback: no state is changed.

When to use it

Use when a scheduled task runs as root, a service user, or a package job rather than the current user.

When not to use it

Do not assume every listed file is executable or valid under run-parts naming rules.

Common misread

System cron files are not the same as a user crontab. Check both before adding duplicate schedules.

crontab -l
find /etc/cron.d /etc/cron.hourly /etc/cron.daily -maxdepth 1 -type f -print

next steps