<para>made fcrontab behave better when there is no space left in the
spool directory (used to truncate the fcrontab source file).
</para>
+ </listitem>
<listitem>
<para>Added a script, check_system_crontabs, to emulate Vixie cron's
behavior about /etc/crontab and /etc/cron.d. Please have a look
<listitem>
<para>added some more checks in fileconf.c: allow user to use
hours, days, hourly, daily, etc options only with %-lines: it is
- ignored if set for a &-line, which is quite confusing for users
+ ignored if set for a &-line, which is quite confusing for users
who may type, for instance "&hourly" instead of
"%hourly".</para>
</listitem>
well, it seems to be more logical like that :)) .</para>
</listitem>
<listitem>
- <para>bug fix: using options first with a &-line may have led to
+ <para>bug fix: using options first with a &-line may have led to
some problems during the first read by fcron (mail send
erroneously if noticenotrun was used, bad set of the first
execution's time and date or immediate execution if bootrun was
</listitem>
<listitem>
<para>bug corrected: fcrontab now defines correctly the remain
- value of a line based on time and date beginning with a "&" but
+ value of a line based on time and date beginning with a "&" but
without runfreq definition.</para>
</listitem>
<listitem>
the time and date of the execution of a job (please see the entry
about system clock adjustment in the present FAQ).</para>
<para>Because of this, on non-Linux systems it is recommended to explicitly 'tell' fcron
- about suspends and the precise suspend duration:
+ about suspends and the precise suspend duration:</para>
<orderedlist>
<listitem>
<para>send a SIGSTOP signal to fcron when going into suspend:
<listitem>
<para>Wake up fcron and tell it to process the suspend file and reschedule tasks accordingly:
<programlisting>$ kill -CONT $(cat &fcron.pid;)</programlisting></para>
+ </listitem>
</orderedlist>
<para>An example script implementing this for pm-utils and systemd is included: fcron.suspend.sh.
Note that it is however not needed on Linux. Contribution of equivalent scripts for other
<link linkend="fcrontab.5">&fcrontab;(5),</link> and choose the
type of line which is the most appropriate for your needs (this is
likely to be a @-line or a %-line).</para>
- <para>On a Debian/Ubuntu, the default /etc/anacrontab looks like:<para>
+ <para>On a Debian/Ubuntu, the default /etc/anacrontab looks like:</para>
<programlisting>1 5 cron.daily nice run-parts --report /etc/cron.daily
7 10 cron.weekly nice run-parts --report /etc/cron.weekly
@monthly 15 cron.monthly nice run-parts --report /etc/cron.monthly
</programlisting>
- <para>A close fcron equivalent would be (see &optserial;):<para>
+ <para>A close fcron equivalent would be (see &optserial;):</para>
<programlisting># Run once a day/week/month, and ensure only one of those tasks is run at a time:
!reset
!serial,nice(10)
%daily * * run-parts --report /etc/cron.daily
%weekly * * run-parts --report /etc/cron.weekly
%monthly * * * run-parts --report /etc/cron.monthly</programlisting>
- <para>Or you could go for something a bit more specific (see &optlavg;, &optnoticenotrun;):<para>
+ <para>Or you could go for something a bit more specific (see &optlavg;, &optnoticenotrun;):</para>
<programlisting># Only run the tasks out of office-hours when the system load is low
# and send an email to the user if fcron couldn't run the job:
!reset
any later version published by the Free Software Foundation; with the Back-Cover
Texts being <!-- ulink hack because this legal notice gets diverted --> <ulink
url="#backcover">Back Cover Text</ulink>. A copy of the license is included in
-<xref linkend="fdl">.</para>
+<xref linkend="fdl" />.</para>
</legalnotice>
<abstract>
<para>&Fcron; is distributed under GPL license (please read the
-license in <xref linkend="gpl">).</para>
+license in <xref linkend="gpl" />).</para>
<para>Project home page: &webpage;</para>
<para>Author: Thibault GODOUET &email;</para>
</abstract>
&Fcron; should be started from <filename>/etc/rc</filename> or
<filename>/etc/rc.local</filename>. Unless the <option>-f</option> (or
<option>--foreground</option>) option is given, it will return immediately, so
-you don't need to start it with '&'.</para>
+you don't need to start it with '&'.</para>
<para>
&Fcron; loads users &fcrontabf;s (see <link
linkend="fcrontab.5">&fcrontab;(5)</link>) files previously installed by
</abstract>
<para>Blank lines, line beginning by a hash sign (#) (which are
considered comments), leading blanks and tabs are ignored. Each line in a
-&fcron.conf file is of the form
+&fcron.conf; file is of the form
<blockquote>
<para>name = value</para>
</blockquote> where the blanks around equal-sign (=) are ignored and
<para>Location of &fcron; pid file (needed by &fcrontab;
to work properly).</para>
</listitem>
+ </varlistentry>
<varlistentry>
<term><varname>suspendfile</varname>=<replaceable>file-path</replaceable>
(<filename>&suspendfile;</filename>)</term>
<varlistentry>
<term><filename>&etc;/&fcron.conf.location;</filename></term>
<listitem>
- <para>Configuration file for &fcron;, &fcrontab and
+ <para>Configuration file for &fcron;, &fcrontab; and
&fcrondyn;: contains paths (spool dir, pid file) and default programs to use
-(editor, shell, etc). See <link linkend="fcron.conf.5">&fcron.conf</link>(5) for
+(editor, shell, etc). See <link linkend="fcron.conf.5">&fcron.conf;</link>(5) for
more details.</para>
</listitem>
</varlistentry>
<refsect2 id="fcrontab.5.tadent">
<title>Entries based on time and date</title>
<para>The second type of &fcrontabf;'s entries begins by an optional
-"&", which can be immediately followed by an optional number defining the
+"&", which can be immediately followed by an optional number defining the
frequency of execution (this is equivalent to option &optrunfreq;) or a
declaration of options; it has five time and date fields, and a shell command
:</para>
<para>The options can be set either for every line below the
declaration or for an individual line. In the first case, the setting is done on
a whole line immediately after an exclamation mark (!), while it is done after a
-"&", a "%" or a "@" depending on the type of scheduling in the second case. Note
+"&", a "%" or a "@" depending on the type of scheduling in the second case. Note
that an option declaration in a schedule overrides the global declaration of
that same option.</para>
<para>Options are separated by commas (,) and their arguments, if
<term>b</term>
<listitem>
<para><emphasis><type>boolean</type></emphasis>(<constant>false</constant>)</para>
- <para>Run an &-line at &fcron;'s startup (or system's resume after suspend/hibernation) if it should
+ <para>Run an &-line at &fcron;'s startup (or system's resume after suspend/hibernation) if it should
have run during system down time.</para>
</listitem>
</varlistentry>
<term>jitter</term>
<listitem>
<para><emphasis><type>integer</type></emphasis>(<constant>0</constant>)</para>
- <para>Run the task between 0 and jitter seconds later than it should have been run. This options only applies to &-lines and is intended for systems where many jobs are supposed to be started at the same minute: the jitter option will randomly spread the start of all those jobs across the first jitter seconds of the minute instead of starting all of them at the first second of the minute. The argument must be between 0 and 255 (inclusive).</para>
+ <para>Run the task between 0 and jitter seconds later than it should have been run. This options only applies to &-lines and is intended for systems where many jobs are supposed to be started at the same minute: the jitter option will randomly spread the start of all those jobs across the first jitter seconds of the minute instead of starting all of them at the first second of the minute. The argument must be between 0 and 255 (inclusive).</para>
<para>&seealso; option &optrandom;.</para>
</listitem>
</varlistentry>
<listitem>
<para><emphasis><type>boolean</type></emphasis>(<constant>false</constant>)</para>
<para>Should &fcron; mail user to report the
-non-execution of a %-job or an &-job? (because of system down state (including suspend/hibernation) for both or
+non-execution of a %-job or an &-job? (because of system down state (including suspend/hibernation) for both or
a too high system load average for the latter)</para>
<para>&seealso; options &optlavg;, &optstrict;.</para>
</listitem>
<para>If set to true, the task will be run at system startup (i.e. immediately after the &argfirstsleep; delay -- by default, &firstsleep; seconds -- when the &fcron; daemon starts the first time after the OS has booted). This is in addition to the regular schedule which won't be modified by this option.</para>
<para>For instance, if a program should be started automatically and run from 7am to 6pm, you could use the following dfcrontab definitions:</para>
<programlisting>&runatreboot 0 6 * * 1-5 start_my_program.sh
-& 0 7 * * 1-5 stop_my_program.sh</programlisting>
+& 0 7 * * 1-5 stop_my_program.sh</programlisting>
<para>&seealso; options &optvolatile;, &optrunonce;, &optrebootreset;.</para>
</listitem>
</varlistentry>
<para>WARNING: this option is deprecated: use option timezone instead!</para>
<para>Time zone difference (in hours, between -24 and
24) between the system time, and the local real time. This option allows a user
-to define its & and %-lines in the local time. Note that this value is set for a
+to define its & and %-lines in the local time. Note that this value is set for a
whole fcrontab file, and only the last definition is taken into account. tzdiff is quite stupid: it doesn't handle daylight saving changes, while option timezone does, so you should use the latter.</para>
<para>&seealso; options &opttimezone;.</para>
</listitem>
5 9 * * sat,sun echo "Good morning Thibault!"
# run every even days of march at 18:00, except on 16th
-0 18 2-30/2~16 Mar * echo "It's time to go back home!"
+0 18 2-30/2~16 Mar * echo "It's time to go back home!"
# the line above is equivalent to
-& 0 18 2-30/2~16 Mar * echo "It's time to go back home!"
+& 0 18 2-30/2~16 Mar * echo "It's time to go back home!"
# reset options to default and set runfreq for lines below
!reset,runfreq(7)
# run once every 7 matches (thanks to the declaration above),
# so if system is running every day at 10:00, this will be
# run once a week
-& 0 10 * * * echo "if you got this message last time 7 days ago,\
+& 0 10 * * * echo "if you got this message last time 7 days ago,\
this computer has been running every day at 10:00 last week.\
If you got the message 8 days ago, then the system has been down \
one day at 10:00 since you got it, etc"
<listitem>
<para>Configuration file for &fcron;, &fcrontab; and
&fcrondyn;: contains paths (spool dir, pid file) and default programs to use
-(editor, shell, etc). See <link linkend="fcron.conf.5">&fcron.conf(5)</link> for
+(editor, shell, etc). See <link linkend="fcron.conf.5">&fcron.conf;(5)</link> for
more details.</para>
</listitem>
</varlistentry>
projects / thirdparty / fcron.git / commitdiff
