From 03e2a7df172fc103b682a90a97f241dd69012579 Mon Sep 17 00:00:00 2001 From: thib Date: Sun, 31 Mar 2002 15:10:09 +0000 Subject: [PATCH] added secondes in time-value added options volatile and stdout updated first option description --- doc/en/fcrontab.5.sgml | 24 ++++++++++++++++++++++-- 1 file changed, 22 insertions(+), 2 deletions(-) diff --git a/doc/en/fcrontab.5.sgml b/doc/en/fcrontab.5.sgml index 5fd2b96..d3688b5 100644 --- a/doc/en/fcrontab.5.sgml +++ b/doc/en/fcrontab.5.sgml @@ -8,7 +8,7 @@ Foundation. A copy of the license is included in gfdl.sgml. --> - + @@ -88,6 +88,10 @@ A copy of the license is included in gfdl.sgml. hours (60 minutes) : h + + seconds : + s + @@ -301,7 +305,7 @@ A copy of the license is included in gfdl.sgml. f time-value - Delay before first execution of a job based on system up time ("@"-lines). Useful in the following case : you have several jobs running, say, every hour. By setting different first value for each job, you can avoid them to run simultaneously everytime. + Delay before first execution of a job based on system up time ("@"-lines). Useful in the following case : you have several jobs running, say, every hour. By setting different first value for each job, you can avoid them to run simultaneously everytime. You can also set it to 0, which is useful when used in conjunction with option &optvolatile;. @@ -457,6 +461,22 @@ A copy of the license is included in gfdl.sgml. In a line run periodically, this option answers the question : should this job be run as soon as possible in its interval of execution (safer), or should fcron set a random time of execution in that interval ? Note that if this option is set, the job may not run if fcron is not running during all the execution interval. Besides, you must know that the random scheme may be quite easy to guess for skilled people. + + volatile + + boolean(0) + When set to true, the job is based on a "volatile" system up time, i.e. restart counting each time fcron is started, which is useful when fcron is started by a script running only, for instance, during a dialup connection : the "volatile" system up time then refers to the dialup connection time. You may also want to use option &optfirst; if you use fcron that way. + &seealso; options &optfirst;, &optstdout;, lines based on elapsed system up time, fcron's option in &fcron;(8). + + + + stdout + + boolean(0) + If fcron is running in the forground, then also let jobs print to stderr/stdout instead of mailing or discarding it. + &seealso; fcron's option in &fcron;(8). + + A boolean argument can be inexistent, in which case brackets are not used and it means true; the string "true", "yes" or 1 to mean true; and the string "false", "no" or 0 to mean false. See above for explanations about time value (section "entries based on elapsed system up time"). Note that dayand and dayor are in fact the same option : a false value to dayand is equivalent to a true to dayor, and reciprocally a false value to dayor is equivalent a true value to dayand. It is the same for lavgand and lavgor. -- 2.40.0