Pio2pio: Created page with "= RHEL8 = cat /etc/crontab SHELL=/bin/bash PATH=/sbin:/bin:/usr/sbin:/usr/bin MAILTO=root # For details see man 4 crontabs # Example of job definition..."

2019-11-21T22:07:13Z

Created page with "= RHEL8 = <source lang=crontab> cat /etc/crontab SHELL=/bin/bash PATH=/sbin:/bin:/usr/sbin:/usr/bin MAILTO=root # For details see man 4 crontabs # Example of job definition..."

New page

= RHEL8 =
<source lang=crontab>
cat /etc/crontab
SHELL=/bin/bash
PATH=/sbin:/bin:/usr/sbin:/usr/bin
MAILTO=root

# For details see man 4 crontabs

# Example of job definition:
# .---------------- minute (0 - 59)
# | .------------- hour (0 - 23)
# | | .---------- day of month (1 - 31)
# | | | .------- month (1 - 12) OR jan,feb,mar,apr ...
# | | | | .---- day of week (0 - 6) (Sunday=0 or 7) OR sun,mon,tue,wed,thu,fri,sat
# | | | | |
# * * * * * user-name command to be executed
</source>

;Cron's locations
<code>/var/spool/cron</code> is where the individual user crontabs live. As user, <code>crontab -e</code> edits the corresponding file in <code>/var/spool/cron</code>.

<code>/etc/cron.d</code> is a directory that is scanned for modular crontab files. The syntax is slightly different for files in that directory. The cron entries have an additional field for a user to run the cron entries as. This is the same as a systemwide <code>/etc/crontab</code> file.

Adding that the files in <code>/etc/cron.d/</code> are, in effect, all root-owned (and therefore not user cron files); also, these files are NOT run '''by cron''' - they are run by a cron '''job''' that looks at these files.

Linux - crontab - Revision history

Pio2pio: Created page with "= RHEL8 = cat /etc/crontab SHELL=/bin/bash PATH=/sbin:/bin:/usr/sbin:/usr/bin MAILTO=root # For details see man 4 crontabs # Example of job definition..."