From Fedora Project Wiki
(Justification for crontabs requirement/fix crontabs package name) |
|||
| (11 intermediate revisions by one other user not shown) | |||
| Line 11: | Line 11: | ||
Packages with cron job files must be placed respectfully into one or more of the following directories /etc/cron.hourly, /etc/cron.daily, /etc/cron.weekly, /etc/cron.monthly depending on the intended interval they should run. | Packages with cron job files must be placed respectfully into one or more of the following directories /etc/cron.hourly, /etc/cron.daily, /etc/cron.weekly, /etc/cron.monthly depending on the intended interval they should run. | ||
If a certain cron job has to be executed at some frequency or at a specific time interval other then the above, that cron job file should be placed in /etc/cron.d directory. | If a certain cron job has to be executed at some frequency or at a specific time interval other then the above, that cron job file should be placed in /etc/cron.d directory followed by an crontab entry at the required interval in the /etc/crontab file. | ||
All files installed in any of these directories must be scripts and must be treated as configuration files so that they can easily be modified by the local system administrator. | All files installed in any of these directories must be scripts and must be treated as configuration files so that they can easily be modified by the local system administrator. | ||
== | == Cron Job file == | ||
An typical cron job file is just an script like | |||
<pre> | |||
#!/bin/sh | |||
# My cron job script | |||
# set -x | |||
echo "This is my simple cron job script" | |||
exit 0 | |||
</pre> | |||
Example of cron job definition run at ever other hour specified in /etc/crontab | |||
<pre> | |||
# .---------------- minute (0 - 59) | # .---------------- minute (0 - 59) | ||
# | .------------- hour (0 - 23) | # | .------------- hour (0 - 23) | ||
| Line 33: | Line 40: | ||
# * * * * * user-name command to be executed | # * * * * * user-name command to be executed | ||
0 */2 * * * root /etc/cron.d/example | |||
</pre> | </pre> | ||
== Cron job file names == | == Cron job file names == | ||
| Line 88: | Line 52: | ||
{{admon/tip|A cron job file name cannot include any period or plus characters as this will cause cron to ignore the file. Underscores should be used instead.}} | {{admon/tip|A cron job file name cannot include any period or plus characters as this will cause cron to ignore the file. Underscores should be used instead.}} | ||
== | == Cron Job Files Packaging == | ||
If an package is going to provide | If an package is going to provide cron job file(s) then it must be placed into a separate $name-cron subpackage. | ||
The file name of a cron job file should match the name of the package from which it comes. | |||
A package containing a cron job must depend on the <code>crontabs</code> package. Since <code>crontabs</code> requires <code>/etc/cron.d</code> and all cron daemon packages create (and own) that directory, <code>crontabs</code> serves as a virtual provide for cron daemon functionality. | |||
</ | |||
=== Example of | === Example of cron job subpackage === | ||
<pre> | <pre> | ||
Name: | Name: | ||
..... | ..... | ||
Source1: %{name}. | Source1: %{name}.cron | ||
%package example- | %package example-cron | ||
Summary: | Summary: Cron job file for %{name} | ||
Group: System Environment/Base | Group: System Environment/Base | ||
Requires: %{name} = %{version}-%{release} | Requires: %{name} = %{version}-%{release} | ||
Requires: | Requires: crontabs | ||
%description example- | %description example-cron | ||
Cron job file for %{name} | |||
%install | %install | ||
mkdir -p $RPM_BUILD_ROOT | mkdir -p $RPM_BUILD_ROOT%{_sysconfdir}/cron.daily | ||
%{__install} -p -D -m 0750 %{SOURCE1} $RPM_BUILD_ROOT%{_sysconfdir}/cron.daily/%{name} | |||
%{__install} -p -D -m | |||
%files example- | %files example-cron | ||
%config(noreplace) %{_sysconfdir}/ | %config(noreplace) %{_sysconfdir}/cron.daily/%{name} | ||
</pre> | </pre> | ||
Latest revision as of 16:44, 27 March 2013
Fedora Cron Job Files
This document describes the guidelines for packaging cron job file(s), in Fedora.
For the purposes of these guidelines, a cron job file is defined as an script (e.g., shell scripts or Perl scripts).
If your package requires regularly scheduled tasks to operate properly and does not ship systemd unit file, you can use those files to set that up.
Cron Job Files on the filesystem
Packages with cron job files must be placed respectfully into one or more of the following directories /etc/cron.hourly, /etc/cron.daily, /etc/cron.weekly, /etc/cron.monthly depending on the intended interval they should run.
If a certain cron job has to be executed at some frequency or at a specific time interval other then the above, that cron job file should be placed in /etc/cron.d directory followed by an crontab entry at the required interval in the /etc/crontab file.
All files installed in any of these directories must be scripts and must be treated as configuration files so that they can easily be modified by the local system administrator.
Cron Job file
An typical cron job file is just an script like
#!/bin/sh # My cron job script # set -x echo "This is my simple cron job script" exit 0
Example of cron job definition run at ever other hour specified in /etc/crontab
# .---------------- 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 0 */2 * * * root /etc/cron.d/example
Cron job file names
The file name of a cron job file should match the name of the package from which it comes.
If a package supplies multiple cron job files files in the same directory, the file names should all start with the name of the package by a hyphen (-) and a suitable suffix.
A cron job file name cannot include any period or plus characters as this will cause cron to ignore the file. Underscores should be used instead.
Cron Job Files Packaging
If an package is going to provide cron job file(s) then it must be placed into a separate $name-cron subpackage.
The file name of a cron job file should match the name of the package from which it comes.
A package containing a cron job must depend on the crontabs package. Since crontabs requires /etc/cron.d and all cron daemon packages create (and own) that directory, crontabs serves as a virtual provide for cron daemon functionality.
Example of cron job subpackage
Name:
.....
Source1: %{name}.cron
%package example-cron
Summary: Cron job file for %{name}
Group: System Environment/Base
Requires: %{name} = %{version}-%{release}
Requires: crontabs
%description example-cron
Cron job file for %{name}
%install
mkdir -p $RPM_BUILD_ROOT%{_sysconfdir}/cron.daily
%{__install} -p -D -m 0750 %{SOURCE1} $RPM_BUILD_ROOT%{_sysconfdir}/cron.daily/%{name}
%files example-cron
%config(noreplace) %{_sysconfdir}/cron.daily/%{name}