Package: cron
Version: 3.0pl1-130
Severity: minor
Tags: patch
Dear Maintainer,
(The patch is in the attachment)
Input file is crontab.5
mandoc: crontab.5:19:4: STYLE: whitespace at end of input line
mandoc: crontab.5:59:14: STYLE: whitespace at end of input line
mandoc: crontab.5:61:10: STYLE: whitespace at end of input line
mandoc: crontab.5:78:76: STYLE: whitespace at end of input line
mandoc: crontab.5:88:75: STYLE: whitespace at end of input line
mandoc: crontab.5:107:47: STYLE: whitespace at end of input line
mandoc: crontab.5:115:62: STYLE: whitespace at end of input line
mandoc: crontab.5:125:77: STYLE: whitespace at end of input line
mandoc: crontab.5:134:65: STYLE: whitespace at end of input line
mandoc: crontab.5:270:74: STYLE: whitespace at end of input line
mandoc: crontab.5:272:21: STYLE: whitespace at end of input line
mandoc: crontab.5:277:59: STYLE: whitespace at end of input line
mandoc: crontab.5:346:67: STYLE: whitespace at end of input line
mandoc: crontab.5:348:50: STYLE: whitespace at end of input line
mandoc: crontab.5:364:4: STYLE: whitespace at end of input line
mandoc: crontab.5:376:64: STYLE: whitespace at end of input line
mandoc: crontab.5:379:13: STYLE: whitespace at end of input line
mandoc: crontab.5:395:43: STYLE: whitespace at end of input line
mandoc: crontab.5:20:15: WARNING: cannot parse date, using it verbatim: 19
April 2010
mandoc: crontab.5:152:6: WARNING: tab in filled text
mandoc: crontab.5:154:6: WARNING: tab in filled text
mandoc: crontab.5:156:7: WARNING: tab in filled text
mandoc: crontab.5:158:5: WARNING: tab in filled text
mandoc: crontab.5:160:13: WARNING: tab in filled text
mandoc: crontab.5:162:6: WARNING: tab in filled text
mandoc: crontab.5:164:12: WARNING: tab in filled text
mandoc: crontab.5:216:7: WARNING: tab in filled text
mandoc: crontab.5:218:7: WARNING: tab in filled text
mandoc: crontab.5:220:8: WARNING: tab in filled text
mandoc: crontab.5:222:8: WARNING: tab in filled text
mandoc: crontab.5:224:10: WARNING: tab in filled text
mandoc: crontab.5:226:9: WARNING: tab in filled text
mandoc: crontab.5:228:8: WARNING: tab in filled text
mandoc: crontab.5:230:7: WARNING: tab in filled text
mandoc: crontab.5:232:10: WARNING: tab in filled text
mandoc: crontab.5:234:8: WARNING: tab in filled text
#######
Test nr. 1:
Remove space at end of lines to simplify other automatic tests to improve
typesetting.
Use "git apply ... --whitespace=fix" to fix extra space issues, or use
global configuration "core.whitespace".
19:.\"
59:be used. The
61:string is
78:many shells will treat the tilde(~) as substitution of $HOME, so if you use
88:SHELL is set to /bin/sh, and LOGNAME and HOME are set from the /etc/passwd
107:module, and loads the environment specified by
115:override the settings described above nor any settings in the
125:variables are set, or the locale specified by the LC_* environment
variables
134:followed by a command, followed by a newline character ('\\n').
270:All the above examples run non-interactive programs. If you wish to run a
272:environment variable
277:.\" work in all systems, as notify-send might require also
346:daemon runs with a defined timezone. It currently does not support
348:configured timezone. Even if a user specifies the
364:The
376:required. Useful tools that could be used for date analysis are
379:.I calendar
395:Paul Vixie <[email protected]> is the author of
#####
Test nr. 2:
Enable and fix warnings from 'test-groff'.
Input file is /tmp/crontab.5
<standard input>:108 (macro IR): only 1 argument, but more are expected
chk_manuals: Output is from: test-groff -Tutf8 -b -e -mandoc -rF0 -t -w w -z
#####
Test nr. 5:
Change '-' to '\(en' (en-dash) for a numeric range.
crontab.5:156:minute 0-59
crontab.5:158:hour 0-23
crontab.5:160:day of month 1-31
crontab.5:162:month 1-12 (or names, see below)
crontab.5:164:day of week 0-7 (0 or 7 is Sun, or use names)
crontab.5:171:8-11 for an ``hours'' entry specifies execution at hours 8, 9, 10
crontab.5:175:separated by commas. Examples: ``1,2,5,9'', ``0-4,8-12''.
crontab.5:179:through the range. For example, ``0-23/2'' can be used in the
hours
crontab.5:260:0 22 * * 1-5 mail \-s "It's 10pm" joe%Joe,%%Where are your
kids?%
crontab.5:261:23 0-23/2 * * * echo "run 23 minutes after midn, 2am, 4am ...,
everyday"
crontab.5:266:0 4 8-14 * * test $(date +\\%u) \-eq 6 && echo "2nd Saturday"
crontab.5:326:Lists and ranges are allowed to co-exist in the same field.
"1-3,7-9" would
crontab.5:327:be rejected by AT&T or BSD cron -- they want to see "1-3" or
"7,8,9" ONLY.
crontab.5:329:Ranges can include "steps", so "1-9/2" is the same as "1,3,5,7,9".
crontab.5:384:0 4 * * Sat [ "$(date +\\%e)" = "$(LANG=C ncal | sed -n 's/^Sa
.* \\([0-9]\\+\\) *$/\\1/p')" ] && echo "Last Saturday" && program_to_run
#####
Test nr. 6:
Change two HYPHEN-MINUSES (code 0x055, 2D) to an em-dash (\[em]), if one
is intended. An en-dash is usually surrounded by a space, while an em-dash
is used without spaces. "man" (1 byte characters) transforms an en-dash
(\[en] to one HYPHEN-MINUS, and an em-dash to two HYPHEN-MINUSES without
considering the space around it.
257:# run at 2:15pm on the first of every month -- output mailed to paul
327:be rejected by AT&T or BSD cron -- they want to see "1-3" or "7,8,9" ONLY.
#####
Test nr. 8:
Protect a full stop (.) with "\&", if it has a blank (white-space) in front
of or (ignoring transparent characters to the full stop) after it, and it does
not mean an end of a sentence.
124:is started up - i.e. either the default system locale, if no LC_*
environment
390:last entry in a crontab is missing a newline (i.e. terminated by EOF), cron
will
#####
Test nr. 15:
Change the name of a macro for two fonts (e.g., BR and IR) to one letter,
if there is only one argument.
Add the second argument if needed. It is sometimes part of the first one.
108:.IR /etc/environment
#####
Test nr. 19:
Use "\e" to print the escape character instead of "\\" (which gets
interpretet in copy mode).
134:followed by a command, followed by a newline character ('\\n').
196:(\\), will be changed into newline characters, and all data
199:lines, like the shell's trailing "\\".
266:0 4 8-14 * * test $(date +\\%u) \-eq 6 && echo "2nd Saturday"
384:0 4 * * Sat [ "$(date +\\%e)" = "$(LANG=C ncal | sed -n 's/^Sa .*
\\([0-9]\\+\\) *$/\\1/p')" ] && echo "Last Saturday" && program_to_run
#####
Test nr. 22:
Remove space in the first column, if not indented.
Use '.in +<number>n' and '.in', '.nf' and '.fi' for an extra indention.
47: name = value
66: PATH = $HOME/bin:$PATH
70: A=1
71: B=2
72: C=$A $B
82: SHELL=/bin/bash
83: PATH=~/bin:/usr/bin/:/bin
#####
Test nr. 24:
Change a HYPHEN-MINUS (code 0x55, 2D) to a minus (\-), if in front of a
name for an option.
384:0 4 * * Sat [ "$(date +\\%e)" = "$(LANG=C ncal | sed -n 's/^Sa .*
\\([0-9]\\+\\) *$/\\1/p')" ] && echo "Last Saturday" && program_to_run
#####
Test nr. 27:
Split lines longer than 80 characters into two or more
lines. Apropriate break points are the end of a sentence or subordinate
clause.
crontab.5: line 305 length 86
crontab.5: line 309 length 96
crontab.5: line 310 length 97
crontab.5: line 311 length 98
crontab.5: line 384 length 138
#####
Test nr. 28:
Wrong distance between sentences or protect the indicator.
1) Separate the sentences and subordinate clauses; each begins on a new
line. See man-pages(7) and "info groff".
Or
2) Adjust space between sentences (two spaces),
3) or protect the indicator by adding "\&" after it.
The "indicator" is an "end-of-sentence character" (.!?).
57:leading or trailing blanks. To define an empty variable, quotes
59:be used. The
68:will not work as you might expect. And neither will this work
89:line of the crontab's owner. PATH is set to "/usr/bin:/bin".
101:recipients by separating recipient users with a comma. If MAILTO is defined
117:file itself. Note in particular that if you want a PATH other than
124:is started up - i.e. either the default system locale, if no LC_*
environment
137:date fields and before the command. The fields may be separated
138:by spaces or tabs. The maximum permitted length for the command field is
198:input. There is no way to split a single command line onto multiple
209:month, plus every Friday. One can, however, achieve the desired result
270:All the above examples run non-interactive programs. If you wish to run a
287:The following lists the content of a regular system-wide crontab file.
Unlike a
294:# and files in /etc/cron.d. These files also have username fields,
315:Note that all the system-wide tasks will run, by default, from 6 am to 7
am. In
346:daemon runs with a defined timezone. It currently does not support
347:per-user timezones. All the tasks: system's and user's will be run based on
the
348:configured timezone. Even if a user specifies the
358:a *. However, this implementation only checks if the
360:is a *. This is why "0 0 */2 * sun" runs every Sunday that's an
367:imagine. For example, it is not straightforward to define the last
376:required. Useful tools that could be used for date analysis are
389:cron requires that each entry in a crontab end in a newline character. If
the
390:last entry in a crontab is missing a newline (i.e. terminated by EOF), cron
will
391:consider the crontab (at least partially) broken. A warning will be written
to
397:and original creator of this manual page. This page has also been modified
for
#####
Test nr. 30:
Surround a block of comments with the macros ".ig" and "..".
The .\" (\#) at the beginning of each line is then not needed.
Makes it easier to add and remove text and adjust lengtxh of lines.
NO PATCH
1:.\"/* Copyright 1988,1990,1993,1994 by Paul Vixie
2:.\" * All rights reserved
3:.\" *
4:.\" * Distribute freely, except: don't remove my name from the source or
5:.\" * documentation (don't take credit for my work), mark your changes (don't
6:.\" * get me blamed for your possible bugs), don't alter or remove this
7:.\" * notice. May be sold if buildable source is provided to buyer. No
8:.\" * warrantee of any kind, express or implied, is included with this
9:.\" * software; use at your own risk, responsibility for damages (if any) to
10:.\" * anyone resulting from the use of this software rests entirely with the
11:.\" * user.
12:.\" *
13:.\" * Send bug reports, bug fixes, enhancements, requests, flames, etc., and
14:.\" * I'll try to keep a version up to date. I can be reached as follows:
15:.\" * Paul Vixie <[email protected]> uunet!decwrl!vixie!paul
16:.\" */
17:.\"
18:.\" $Id: crontab.5,v 2.4 1994/01/15 20:43:43 vixie Exp $
19:.\"
276:.\" Note: Based on some web searches, below example might not fully
277:.\" work in all systems, as notify-send might require also
278:.\" to have knowledge of the dbus session in use (through the environment)
279:.\" However, adding that code here is an overkill
#####
-- System Information:
Debian Release: buster/sid
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500,
'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.9.80-2 (SMP w/2 CPU cores)
Locale: LANG=is_IS.iso88591, LC_CTYPE=is_IS.iso88591 (charmap=ISO-8859-1),
LANGUAGE=is_IS.iso88591 (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
Versions of packages cron depends on:
ii adduser 3.117
ii debianutils 4.8.4
ii dpkg 1.19.0.5
ii libc6 2.27-2
ii libpam-runtime 1.1.8-3.7
ii libpam0g 1.1.8-3.7
ii libselinux1 2.7-2+b1
ii lsb-base 9.20170808
Versions of packages cron recommends:
ii exim4 4.90.1-2
ii exim4-daemon-light [mail-transport-agent] 4.90.1-2
Versions of packages cron suggests:
ii anacron 2.3-24
pn checksecurity <none>
ii logrotate 3.11.0-0.1
Versions of packages cron is related to:
pn libnss-ldap <none>
pn libnss-ldapd <none>
pn libpam-ldap <none>
pn libpam-mount <none>
pn nis <none>
pn nscd <none>
-- no debconf information
--
Bjarni I. Gislason
--- crontab.5 2018-03-19 23:49:40.000000000 +0000
+++ crontab.5.new 2018-03-20 00:35:17.000000000 +0000
@@ -16,7 +16,7 @@
.\" */
.\"
.\" $Id: crontab.5,v 2.4 1994/01/15 20:43:43 vixie Exp $
-.\"
+.\"
.TH CRONTAB 5 "19 April 2010"
.UC 4
.SH NAME
@@ -44,7 +44,9 @@ command. The crontab file is parsed fro
settings will affect only the cron commands below them in the file.
An environment setting is of the form,
.PP
- name = value
+.in +4n
+name = value
+.in
.PP
where the spaces around the equal-sign (=) are optional, and any subsequent
non-leading spaces in
@@ -54,39 +56,49 @@ will be part of the value assigned to
The
.I value
string may be placed in quotes (single or double, but matching) to preserve
-leading or trailing blanks. To define an empty variable, quotes
+leading or trailing blanks. To define an empty variable, quotes
.B must
-be used. The
+be used. The
.I value
-string is
+string is
.B not
parsed for environmental substitutions or replacement of variables, thus lines
like
.PP
- PATH = $HOME/bin:$PATH
+.in +4n
+PATH = $HOME/bin:$PATH
+.in
.PP
-will not work as you might expect. And neither will this work
+will not work as you might expect. And neither will this work
.PP
- A=1
- B=2
- C=$A $B
+.in +4n
+.nf
+A=1
+B=2
+C=$A $B
+.fi
+.in
.PP
There will not be any substitution for the defined variables in the
last value.
.PP
An alternative for setting up the commands path is using the fact that
-many shells will treat the tilde(~) as substitution of $HOME, so if you use
+many shells will treat the tilde(~) as substitution of $HOME, so if you use
.I bash
for your tasks you can use this:
.PP
- SHELL=/bin/bash
- PATH=~/bin:/usr/bin/:/bin
+.in +4n
+.nf
+SHELL=/bin/bash
+PATH=~/bin:/usr/bin/:/bin
+.fi
+.in
.PP
Several environment variables are set up automatically by the
.IR cron (8)
daemon.
-SHELL is set to /bin/sh, and LOGNAME and HOME are set from the /etc/passwd
-line of the crontab's owner. PATH is set to "/usr/bin:/bin".
+SHELL is set to /bin/sh, and LOGNAME and HOME are set from the /etc/passwd
+line of the crontab's owner. PATH is set to "/usr/bin:/bin".
HOME, SHELL, and PATH may be overridden by settings in the crontab;
LOGNAME is the user that the job is running from, and may not be changed.
.PP
@@ -98,31 +110,32 @@ In addition to LOGNAME, HOME, and SHELL,
will look at MAILTO if it has any reason to send mail as a result of running
commands in ``this'' crontab. If MAILTO is defined (and non-empty), mail is
sent to the user so named. MAILTO may also be used to direct mail to multiple
-recipients by separating recipient users with a comma. If MAILTO is defined
+recipients by separating recipient users with a comma. If MAILTO is defined
but empty (MAILTO=""), no mail will be sent. Otherwise mail is sent to the
owner of the crontab.
.PP
On the Debian GNU/Linux system, cron supports the
.B pam_env
-module, and loads the environment specified by
-.IR /etc/environment
+module, and loads the environment specified by
+.I /etc/environment
and
.IR /etc/security/pam_env.conf .
It also reads locale information from
.IR /etc/default/locale .
However, the PAM settings do
.B NOT
-override the settings described above nor any settings in the
+override the settings described above nor any settings in the
.I crontab
-file itself. Note in particular that if you want a PATH other than
+file itself. Note in particular that if you want a PATH other than
"/usr/bin:/bin", you will need to set it in the crontab file.
.PP
By default, cron will send mail using the mail "Content-Type:" header of
"text/plain" with the "charset=" parameter set to the charmap / codeset of the
locale in which
.IR crond (8)
-is started up - i.e. either the default system locale, if no LC_* environment
-variables are set, or the locale specified by the LC_* environment variables
+is started up \(en i.e.\& either the default system locale,
+if no LC_* environment variables are set, or the locale specified by
+the LC_* environment variables
( see
.IR locale (7) ).
You can use different character encodings for mailed cron job output by
@@ -131,11 +144,11 @@ to the correct values of the mail header
.PP
The format of a cron command is very much the V7 standard, with a number of
upward-compatible extensions. Each line has five time and date fields,
-followed by a command, followed by a newline character ('\\n').
+followed by a command, followed by a newline character ('\en').
The system crontab (/etc/crontab) uses the same format, except that
the username for the command is specified after the time and
-date fields and before the command. The fields may be separated
-by spaces or tabs. The maximum permitted length for the command field is
+date fields and before the command. The fields may be separated
+by spaces or tabs. The maximum permitted length for the command field is
998 characters.
.PP
Commands are executed by
@@ -153,30 +166,30 @@ field allowed values
.br
----- --------------
.br
-minute 0-59
+minute 0\(en59
.br
-hour 0-23
+hour 0\(en23
.br
-day of month 1-31
+day of month 1\(en31
.br
-month 1-12 (or names, see below)
+month 1\(en12 (or names, see below)
.br
-day of week 0-7 (0 or 7 is Sun, or use names)
+day of week 0\(en7 (0 or 7 is Sun, or use names)
.br
.PP
A field may be an asterisk (*), which always stands for ``first\-last''.
.PP
Ranges of numbers are allowed. Ranges are two numbers separated
with a hyphen. The specified range is inclusive. For example,
-8-11 for an ``hours'' entry specifies execution at hours 8, 9, 10
+8\(en11 for an ``hours'' entry specifies execution at hours 8, 9, 10
and 11.
.PP
Lists are allowed. A list is a set of numbers (or ranges)
-separated by commas. Examples: ``1,2,5,9'', ``0-4,8-12''.
+separated by commas. Examples: ``1,2,5,9'', ``0\(en4,8\(en12''.
.PP
Step values can be used in conjunction with ranges. Following
a range with ``/<number>'' specifies skips of the number's value
-through the range. For example, ``0-23/2'' can be used in the hours
+through the range. For example, ``0\(en23/2'' can be used in the hours
field to specify command execution every other hour (the alternative
in the V7 standard is ``0,2,4,6,8,10,12,14,16,18,20,22''). Steps are
also permitted after an asterisk, so if you want to say ``every two
@@ -193,10 +206,10 @@ The entire command portion of the line,
character, will be executed by /bin/sh or by the shell
specified in the SHELL variable of the crontab file.
Percent-signs (%) in the command, unless escaped with backslash
-(\\), will be changed into newline characters, and all data
+(\e), will be changed into newline characters, and all data
after the first % will be sent to the command as standard
-input. There is no way to split a single command line onto multiple
-lines, like the shell's trailing "\\".
+input. There is no way to split a single command line onto multiple
+lines, like the shell's trailing "\e".
.PP
Note: The day of a command's execution can be specified by two
fields \(em day of month, and day of week. If both fields are
@@ -206,7 +219,7 @@ field matches the current time. For exa
.br
``30 4 1,15 * 5''
would cause a command to be run at 4:30 am on the 1st and 15th of each
-month, plus every Friday. One can, however, achieve the desired result
+month, plus every Friday. One can, however, achieve the desired result
by adding a test to the command (see the last example in EXAMPLE CRON FILE
below).
.PP
@@ -254,27 +267,27 @@ MAILTO=paul
#
# run five minutes after midnight, every day
5 0 * * * $HOME/bin/daily.job >> $HOME/tmp/out 2>&1
-# run at 2:15pm on the first of every month -- output mailed to paul
+# run at 2:15pm on the first of every month \(em output mailed to paul
15 14 1 * * $HOME/bin/monthly
# run at 10 pm on weekdays, annoy Joe
-0 22 * * 1-5 mail \-s "It's 10pm" joe%Joe,%%Where are your kids?%
-23 0-23/2 * * * echo "run 23 minutes after midn, 2am, 4am ..., everyday"
+0 22 * * 1\(en5 mail \-s "It's 10pm" joe%Joe,%%Where are your kids?%
+23 0\(en23/2 * * * echo "run 23 minutes after midn, 2am, 4am ..., everyday"
5 4 * * sun echo "run at 5 after 4 every Sunday"
0 */4 1 * mon echo "run every 4th hour on the 1st and on every Monday"
0 0 */2 * sun echo "run at midn on every Sunday that's an uneven date"
# Run on every second Saturday of the month
-0 4 8-14 * * test $(date +\\%u) \-eq 6 && echo "2nd Saturday"
+0 4 8\(en14 * * test $(date +\e%u) \-eq 6 && echo "2nd Saturday"
.fi
.PP
-All the above examples run non-interactive programs. If you wish to run a
+All the above examples run non-interactive programs. If you wish to run a
program that interacts with the user's desktop you have to make sure the proper
-environment variable
+environment variable
.I DISPLAY
is set.
.\" Note: Based on some web searches, below example might not fully
-.\" work in all systems, as notify-send might require also
+.\" work in all systems, as notify-send might require also
.\" to have knowledge of the dbus session in use (through the environment)
.\" However, adding that code here is an overkill
.nf
@@ -284,14 +297,14 @@ is set.
.SH EXAMPLE SYSTEM CRON FILE
-The following lists the content of a regular system-wide crontab file. Unlike a
+The following lists the content of a regular system-wide crontab file. Unlike
a
user's crontab, this file has the username field, as used by /etc/crontab.
.nf
# /etc/crontab: system-wide crontab
# Unlike any other crontab you don't have to run the `crontab'
# command to install the new version when you edit this file
-# and files in /etc/cron.d. These files also have username fields,
+# and files in /etc/cron.d. These files also have username fields,
# that none of the other crontabs do.
SHELL=/bin/sh
@@ -312,7 +325,7 @@ PATH=/usr/local/sbin:/usr/local/bin:/sbi
#
.fi
-Note that all the system-wide tasks will run, by default, from 6 am to 7 am. In
+Note that all the system-wide tasks will run, by default, from 6 am to 7 am.
In
the case of systems that are not powered on during that period of time, only
the hourly tasks will be executed unless the defaults above are changed.
@@ -323,10 +336,11 @@ cron(8), crontab(1)
When specifying day of week, both day 0 and day 7 will be considered Sunday.
BSD and AT&T seem to disagree about this.
.PP
-Lists and ranges are allowed to co-exist in the same field. "1-3,7-9" would
-be rejected by AT&T or BSD cron -- they want to see "1-3" or "7,8,9" ONLY.
+Lists and ranges are allowed to co-exist in the same field.
+"1\(en3,7\(en9" would be rejected by AT&T or BSD cron \(em they want
+to see "1\(en3" or "7,8,9" ONLY.
.PP
-Ranges can include "steps", so "1-9/2" is the same as "1,3,5,7,9".
+Ranges can include "steps", so "1\(en9/2" is the same as "1,3,5,7,9".
.PP
Months or days of the week can be specified by name.
.PP
@@ -343,9 +357,9 @@ are extensions.
.SH LIMITATIONS
The
.I cron
-daemon runs with a defined timezone. It currently does not support
-per-user timezones. All the tasks: system's and user's will be run based on the
-configured timezone. Even if a user specifies the
+daemon runs with a defined timezone. It currently does not support
+per-user timezones. All the tasks: system's and user's will be run based on
the
+configured timezone. Even if a user specifies the
.I TZ
environment variable in his
.I crontab
@@ -355,16 +369,16 @@ of the crontab tasks themselves.
POSIX specifies that the day of month and the day of week fields both need to
match the current time if either of them
.I is
-a *. However, this implementation only checks if the
+a *. However, this implementation only checks if the
.I first character
-is a *. This is why "0 0 */2 * sun" runs every Sunday that's an
+is a *. This is why "0 0 */2 * sun" runs every Sunday that's an
uneven date while the POSIX standard would have it run every Sunday and on
every uneven date.
-The
+The
.I crontab
syntax does not make it possible to define all possible periods one can
-imagine. For example, it is not straightforward to define the last
+imagine. For example, it is not straightforward to define the last
weekday of a month.
To have a task run in a time period that cannot be defined using
.I crontab
@@ -373,27 +387,27 @@ date and time information and continue e
matches the desired one.
If the program itself cannot do the checks then a wrapper script would be
-required. Useful tools that could be used for date analysis are
+required. Useful tools that could be used for date analysis are
.I ncal
or
-.I calendar
+.I calendar
For example, to run a program the last Saturday of every month you could use
the following wrapper code:
.nf
-0 4 * * Sat [ "$(date +\\%e)" = "$(LANG=C ncal | sed -n 's/^Sa .*
\\([0-9]\\+\\) *$/\\1/p')" ] && echo "Last Saturday" && program_to_run
+0 4 * * Sat [ "$(date +\e%e)" = "$(LANG=C ncal | sed \-n 's/^Sa .*
\e([0\(en9]\e+\e) *$/\ex1/p')" ] && echo "Last Saturday" && program_to_run
.fi
.SH DIAGNOSTICS
-cron requires that each entry in a crontab end in a newline character. If the
-last entry in a crontab is missing a newline (i.e. terminated by EOF), cron
will
-consider the crontab (at least partially) broken. A warning will be written to
-syslog.
+cron requires that each entry in a crontab end in a newline character. If the
+last entry in a crontab is missing a newline (i.e.\& terminated by EOF),
+cron will consider the crontab (at least partially) broken.
+A warning will be written to syslog.
.SH AUTHOR
-Paul Vixie <[email protected]> is the author of
+Paul Vixie <[email protected]> is the author of
.I cron
-and original creator of this manual page. This page has also been modified for
+and original creator of this manual page. This page has also been modified for
Debian by Steve Greenland, Javier Fernandez-Sanguino, Christian Kastner and
Christian Pekeler.
