Package: cron Version: 3.0pl1-130 Severity: minor Tags: patch Dear Maintainer,
(The patch is in the attachment.) Input file is crontab.1 mandoc: crontab.1:46:35: STYLE: whitespace at end of input line mandoc: crontab.1:50:56: STYLE: whitespace at end of input line mandoc: crontab.1:52:25: STYLE: whitespace at end of input line mandoc: crontab.1:54:35: STYLE: whitespace at end of input line mandoc: crontab.1:56:50: STYLE: whitespace at end of input line mandoc: crontab.1:75:12: STYLE: whitespace at end of input line mandoc: crontab.1:86:15: STYLE: whitespace at end of input line mandoc: crontab.1:110:60: STYLE: whitespace at end of input line mandoc: crontab.1:119:17: STYLE: whitespace at end of input line mandoc: crontab.1:122:55: STYLE: whitespace at end of input line mandoc: crontab.1:161:16: STYLE: whitespace at end of input line mandoc: crontab.1:171:43: STYLE: whitespace at end of input line mandoc: crontab.1:20:15: WARNING: cannot parse date, using it verbatim: 19 April 2010 ####### Input file is crontab.1 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". 46:file in order to use this command. 50:command, or all users will be able to use this command. 52:If both files exist then 54:takes precedence. Which means that 56:is not considered and your user must be listed in 75:.IR su (8) 86:the note under 110:is to display the three line "DO NOT EDIT THIS FILE" header 119:behaviour of the 122:original behaviour by setting the environment variable 161:The files under 171:Paul Vixie <p...@vix.com> is the author of ##### 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. 117:non-idempotent -- you keep adding copies of the header. This causes ##### Test nr. 24: Change a HYPHEN-MINUS (code 0x55, 2D) to a minus (\-), if in front of a name for an option. 65:.I -u 77:.I -u 84:.I -l 91:.I -r 95:.I -e 104:.I -i 109:.I crontab -l 120:.B -l 125:.I crontab -l ##### 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.1: line 166 length 84 ##### 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" (.!?). 54:takes precedence. Which means that 67:used (when listing) or modified (when editing). If this option is not given, 85:option causes the current crontab to be displayed on standard output. See 99:from the editor, the modified crontab will be installed automatically. If 112:beginning of the crontab when it is installed. The problem is that 117:non-idempotent -- you keep adding copies of the header. This causes 118:pain to scripts that use sed to edit a crontab. Therefore, the default 121:option has been changed to not output such header. You may obtain the 137:directory. Users are not allowed to edit the files under that directory 156:cron requires that each entry in a crontab end in a newline character. If the 164:are named based on the user's account name. Crontab jobs will not be run for 173: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 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 <p...@vix.com> uunet!decwrl!vixie!paul 16:.\" */ 17:.\" 18:.\" $Id: crontab.1,v 2.4 1993/12/31 10:47:33 vixie Exp $ 19:.\" ##### -- 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.1 2018-03-19 23:49:40.000000000 +0000 +++ crontab.1.new 2018-03-20 00:46:07.000000000 +0000 @@ -43,28 +43,28 @@ file does not exist but the .I /etc/cron.deny file does exist, then you must \fBnot\fR be listed in the .I /etc/cron.deny -file in order to use this command. +file in order to use this command. .PP If neither of these files exists, then depending on site-dependent configuration parameters, only the super user will be allowed to use this -command, or all users will be able to use this command. +command, or all users will be able to use this command. .PP -If both files exist then +If both files exist then .I /etc/cron.allow -takes precedence. Which means that +takes precedence. Which means that .I /etc/cron.deny -is not considered and your user must be listed in +is not considered and your user must be listed in .I /etc/cron.allow in order to be able to use the crontab. .PP -Regardless of the existance of any of these files, the root administrative +Regardless of the existence of any of these files, the root administrative user is always allowed to setup a crontab. For standard Debian systems, all users may use this command. .PP If the -.I -u +.I \-u option is given, it specifies the name of the user whose crontab is to be -used (when listing) or modified (when editing). If this option is not given, +used (when listing) or modified (when editing). If this option is not given, .I crontab examines "your" crontab, i.e., the crontab of the person executing the command. Note that @@ -72,57 +72,57 @@ command. Note that can confuse .I crontab and that if you are running inside of -.IR su (8) +.IR su (8) you should always use the -.I -u +.I \-u option for safety's sake. .PP The first form of this command is used to install a new crontab from some named file or standard input if the pseudo-filename ``-'' is given. .PP The -.I -l -option causes the current crontab to be displayed on standard output. See -the note under +.I \-l +option causes the current crontab to be displayed on standard output. See +the note under .B DEBIAN SPECIFIC below. .PP The -.I -r +.I \-r option causes the current crontab to be removed. .PP The -.I -e +.I \-e option is used to edit the current crontab using the editor specified by the \s-1VISUAL\s+1 or \s-1EDITOR\s+1 environment variables. After you exit -from the editor, the modified crontab will be installed automatically. If +from the editor, the modified crontab will be installed automatically. If neither of the environment variables is defined, then the default editor /usr/bin/editor is used. .PP The -.I -i +.I \-i option modifies the \-r option to prompt the user for a 'y/Y' response before actually removing the crontab. .SH DEBIAN SPECIFIC The "out-of-the-box" behaviour for -.I crontab -l -is to display the three line "DO NOT EDIT THIS FILE" header +.I crontab \-l +is to display the three line "DO NOT EDIT THIS FILE" header that is placed at the -beginning of the crontab when it is installed. The problem is that +beginning of the crontab when it is installed. The problem is that it makes the sequence .PP crontab \-l | crontab \- .PP -non-idempotent -- you keep adding copies of the header. This causes -pain to scripts that use sed to edit a crontab. Therefore, the default -behaviour of the -.B -l -option has been changed to not output such header. You may obtain the -original behaviour by setting the environment variable +non-idempotent \(em you keep adding copies of the header. This causes +pain to scripts that use sed to edit a crontab. Therefore, the default +behaviour of the +.B \-l +option has been changed to not output such header. You may obtain the +original behaviour by setting the environment variable .B CRONTAB_NOHEADER to 'N', which will cause the -.I crontab -l +.I crontab \-l command to emit the extraneous header. .SH "SEE ALSO" crontab(5), cron(8) @@ -134,7 +134,7 @@ crontab(5), cron(8) .fi .PP There is one file for each user's crontab under the /var/spool/cron/crontabs -directory. Users are not allowed to edit the files under that directory +directory. Users are not allowed to edit the files under that directory directly to ensure that only users allowed by the system to run periodic tasks can add them, and only syntactically correct crontabs will be written there. This is enforced by having the directory writable only by the @@ -153,22 +153,23 @@ SVR3 syntax. A fairly informative usage message appears if you run it with a bad command line. -cron requires that each entry in a crontab end in a newline character. If the +cron requires that each entry in a crontab end in a newline character. If the last entry in a crontab is missing the newline, cron will consider the crontab (at least partially) broken and refuse to install it. .SH DIAGNOSTICS -The files under +The files under .I /var/spool/cron/crontabs -are named based on the user's account name. Crontab jobs will not be run for -users whose accounts have been renamed either due to changes in the local system -or because they are managed through a central user database (external to the system, -for example an LDAP directory). +are named based on the user's account name. +Crontab jobs will not be run for users whose accounts have been +renamed either due to changes in the local system or because they are +managed through a central user database (external to the system, for +example an LDAP directory). .SH AUTHOR -Paul Vixie <p...@vix.com> is the author of +Paul Vixie <p...@vix.com> 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 and Christian Kastner.
