From: thib Date: Tue, 23 Jan 2007 22:52:09 +0000 (+0000) Subject: added a faq entry for Vixie cron @reboot X-Git-Tag: ver3_0_3-rc1~19 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=1d2951c3f94d00c6aaa5cee39880537d1365ecfa;p=fcron added a faq entry for Vixie cron @reboot updated/corrected "how to emulate anacron entry" --- diff --git a/doc/en/faq.sgml b/doc/en/faq.sgml index 6e99bc2..23d5a63 100644 --- a/doc/en/faq.sgml +++ b/doc/en/faq.sgml @@ -8,7 +8,7 @@ Foundation. A copy of the license is included in gfdl.sgml. --> - + Frequently Asked Questions @@ -341,10 +341,33 @@ and set appropriately the paths: How can I emulate an anacron entry? + + As anacron, fcron does not assume that the system runs permanently. + Thus, fcron features similar functionalities to anacron, but it + has different means to achieve it, in other words other ways to define + when a job should run. Fcron is in general much more flexible + than anacron. That said, + there is no strict equivalent to an anacron entry: the best would + probably be to have a look at + &fcrontab;(5), and choose the + type of line which is the most appropriate for your needs (this is + likely to be a @-line or a %-line). + If you insist on willing to emulate an anacron entry, as precisely + as possible, you should use a %daily, %monthly or %weekly line. If + this doesn't emulate an anacron entry as closely as you would like, + you may want to try a %hours or %days line, and/or &optrunfreq;. + In any case, you would benefit from using fcron options such as + &optserial; or &optlavg;. + + + + + How can I emulate a Vixie cron @reboot entry? + You should use a line similar to the following one: - @volatile,first(xx) BIG-period /your/command - where xx is the time you would have put in your anacron line. + @volatile,first(1) BIG-period /your/command + This will run /your/command one minute after every reboot.