From ab3da6314e9c2abc5fe8aaafc1dbede632a2d33a Mon Sep 17 00:00:00 2001 From: thib Date: Wed, 11 Jan 2006 01:01:18 +0000 Subject: [PATCH] removed spaces before punctuation --- doc/en/faq.sgml | 84 ++++++++++++++++++++++----------------------- doc/en/install.sgml | 16 ++++----- 2 files changed, 50 insertions(+), 50 deletions(-) diff --git a/doc/en/faq.sgml b/doc/en/faq.sgml index 5a37e8e..2d96569 100644 --- a/doc/en/faq.sgml +++ b/doc/en/faq.sgml @@ -1,6 +1,6 @@ - + Frequently Asked Questions This FAQ intends to complement the man pages by following a more practical approach. - If you think a QA should be added, please mail me it ! + If you think a QA should be added, please mail me it! - How does fcron handle system clock adjustments ? + How does fcron handle system clock adjustments? @@ -62,24 +62,24 @@ a big change in the time and date, you should probably reset all the scheduled - How does fcron handle daylight saving time changes ? + How does fcron handle daylight saving time changes? - There are two types of daylight saving time change : + There are two types of daylight saving time change: the remove-one-hour change (for instance, "at 3:00, it will be 2:00"), and the add-one-hour one (for instance, "at 2:00, it will be 3:00"). In both cases, fcron will run the job only once (more precisely, it won't run the job twice as many as it should have). In the first case, the official time changes as follow -(in order of real chronological time) : [x, 2:00] -> i1 : [2:00, 3:00] - -> i2 : [2:00, 3:00] -> [3:00, y]. i1 and i2 are the names of the two +(in order of real chronological time): [x, 2:00] -> i1: [2:00, 3:00] + -> i2: [2:00, 3:00] -> [3:00, y]. i1 and i2 are the names of the two intervals [2:00, 3:00]. For this kind of DST change, a job which should run between 2:00 and 3:00 will run either in i1 or in i2, but not both. Consequently, a job scheduled to run every day at 2:30 (for instance) will be run only once. There is no way for a user to know if the job will be run in i1 or i2. - In the second case, there is a gap in time : -the official time changes as follow (in order of real chronological time) : + In the second case, there is a gap in time: +the official time changes as follow (in order of real chronological time): [x, 2:00] -> [3:00, y]. A job scheduled between 2:00 and 3:00 will get run once, and only once, even if it should have been run several times. For instance, a job which should have run every 10 minutes will run only @@ -92,7 +92,7 @@ every day at 2:30, it will run at 3:30 the day of this kind of DST change. What about fcron and software suspend - (aka. suspend to RAM, to disk) ? + (aka. suspend to RAM, to disk)? We suppose here that you are using swsusp and the hibernate @@ -101,7 +101,7 @@ every day at 2:30, it will run at 3:30 the day of this kind of DST change. When you switch on your computer after a suspend to disk, the system time will be incorrect, and will then be corrected by the hibernate script. Before it is corrected, fcron may - compute the time and date of the next execution of a job : + compute the time and date of the next execution of a job: the computation would then be incorrect (please see the entry about system clock adjustment in the present FAQ). So you should have the hibernate script stop fcron before @@ -115,15 +115,15 @@ every day at 2:30, it will run at 3:30 the day of this kind of DST change. How can I prevent fcrontab from considering the first -"word" of my command line as a user name i.e. "runas(word)" ? +"word" of my command line as a user name i.e. "runas(word)"? Suppose you have an user called "echo" (weird idea ... :)) ). If you use -the line '* * * * * echo "Hello !"' in root's fcrontab, "echo" will be +the line '* * * * * echo "Hello!"' in root's fcrontab, "echo" will be interpreted as "runas(echo)". - To suppress that, put your command in quotes : -* * * * * 'echo "Hello !"' will work as + To suppress that, put your command in quotes: +* * * * * 'echo "Hello!"' will work as expected as quotes are allowed for the shell command but not for the user name. @@ -176,13 +176,13 @@ where: d is the time interval between active task count readings, typically ever - How can I use fcrontab in scripts ? + How can I use fcrontab in scripts? You can use pipes with "fcrontab -l" (list the fcrontab) and "fcrontab -" (read the new fcrontab from -input). For example : +input). For example: echo -e "`fcrontab -l | grep -v exim`\n0 * * * * /usr/sbin/exim -q" | fcrontab - can be used to add a line. Another way to do it would be to: @@ -198,23 +198,23 @@ tmpfile"). Can I use fcron from time to time, for instance in a -script ? +script? Let's suppose you use fcron in your ppp-up script. Fcron can permit you to run some jobs at connection startup, but not at each -connection, like it would be if the job was run directly by the ppp-up script : +connection, like it would be if the job was run directly by the ppp-up script: for instance, only once every week. - Using fcron in a script : running a job once + <title>Using fcron in a script: running a job once every day, week, etc, at dialup connection - You can use a script like : + You can use a script like: # A ppp-up script ... -# run the jobs pending, then returns : +# run the jobs pending, then returns: fcron -f -y -o - in conjunction with a fcrontab file like : + in conjunction with a fcrontab file like: # a fcrontab file ... %random(no),weekly,stdout * * /a/command/to/download/latest/mozilla/release @@ -223,26 +223,26 @@ fcron -f -y -o You can also use fcron to run some jobs until the end of the connection. For instance, you can make fetchmail retrieve mails more often -during connection : we suppose that it is configured to retrieve mails every +during connection: we suppose that it is configured to retrieve mails every hour, which launches a dialup connection if necessary, and we want it to check for mails every 5 minutes while connected. - Using fcron in a script : running a job until the + <title>Using fcron in a script: running a job until the end of the connection - ppp-up script : + ppp-up script: # A ppp-up script ... -# run fcron at the beginning of the connection : +# run fcron at the beginning of the connection: fcron -b - ppp-down script : + ppp-down script: # A ppp-down script ... -# stop fcron at the end of the connection : -# -- Warning : killall may have unwanted effect on non linux systems -- +# stop fcron at the end of the connection: +# -- Warning: killall may have unwanted effect on non linux systems -- killall -TERM fcron - the fcrontab : + the fcrontab: # a fcrontab file ... @volatile,first(0) 5 fetchmail @@ -263,7 +263,7 @@ linkend="fcrontab.5">&fcrontab;(5) - Can I run fcron without root's privileges ? + Can I run fcron without root's privileges? Yes, you can. To do that, see the @@ -272,7 +272,7 @@ without root privileges. First, create a directory where you'll install fcron, - and some subdirectories : + and some subdirectories: bash$ mkdir /home/thib/fcron bash$ cd /home/thib/fcron @@ -281,7 +281,7 @@ without root privileges. Then, run configure with option , set all user names and groups to yours, -and set appropriately the paths : +and set appropriately the paths: This option allows a non privileged user to run fcron. When used, fcron does not change its rights before running a job @@ -304,12 +304,12 @@ and set appropriately the paths : - Has fcron some incompatibilities with Vixie cron ? + Has fcron some incompatibilities with Vixie cron? As far as I know, fcron supports completely the syntax of Vixie cron's crontab, excepted the @* syntax (@annually, - @weekly, etc : if you use that, you will have to replace it + @weekly, etc: if you use that, you will have to replace it with the explicit equivalent given in crontab(5)). So you should not have much problem with that (otherwise, please contact me at &email;). @@ -319,18 +319,18 @@ and set appropriately the paths : As for now, fcron do not do that. Fcron do not support the /etc/cron.d/ dir too, as it is just an extension of the /etc/crontab file. - But be reassured : /etc/cron.{daily,weekly,monthly} are supported + But be reassured: /etc/cron.{daily,weekly,monthly} are supported by fcron (in fact, those dirs are not managed by fcron directly, but by run-parts, which is independent from fcron). So if you want to replace transparently Vixie cron by fcron, all you have to do is creating a /usr/bin/crontab link to /usr/bin/crontab, and to reinstall the system (f)crontab with fcrontab /etc/crontab each time you modify it - (if you find something else to do, please tell me !). + (if you find something else to do, please tell me!). You can also use the script script/check_system_crontabs to generate a system fcrontab from /etc/(f)crontab and /etc/cron.d/, and install it automatically. If you choose to do that, take - a look at the beginning of the script : you will find insctructions + a look at the beginning of the script: you will find insctructions on how to use it -- and a few warnings you should pay attention to. With this script, the behavior of fcron should be very similar to Vixie cron's one concerning /etc/crontab and /etc/cron.d/. @@ -339,10 +339,10 @@ and set appropriately the paths : - How can I emulate an anacron entry ? + How can I emulate an anacron entry? - You should use a line similar to the following one : + 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. diff --git a/doc/en/install.sgml b/doc/en/install.sgml index a8df639..58f524f 100644 --- a/doc/en/install.sgml +++ b/doc/en/install.sgml @@ -1,6 +1,6 @@ - + How to install fcron - uncompress the archive : + uncompress the archive: bash$ tar -xzf fcron-X.Y.Z.src.tar.gz @@ -23,7 +23,7 @@ tar -xzf fcron-X.Y.Z.src.tar.gz bash$ cd fcron-X.Y.Z - run the configure script : + run the configure script: bash$ ./configure @@ -43,7 +43,7 @@ and/or (see "./configure You may also want to change the place where &fcron; will be installed: you can use the configure 's -option to do that. For instance : +option to do that. For instance: ./configure (default is prefix=/usr) @@ -85,7 +85,7 @@ necessary force a value by the options and If you get older &fcron;'s man-pages with man command after having upgraded, it's probably because -&fcron; has changed its default man directory : you should remove manually the +&fcron; has changed its default man directory: you should remove manually the outdated man-pages. @@ -108,12 +108,12 @@ is on the top of the file and clearly delimited). - compile : + compile: bash$ make - then install binaries as root : + then install binaries as root: bash$ su root bash# make install -- 2.40.0