Package: cron Version: 3.0pl1-195 Severity: minor Tags: patch Dear cron maintainer, the manpage-l10n project[1] maintains a large number of translations of man pages both from a large variety of sources (including cron) as well for a large variety of target languages.
During their work translators notice different possible issues in the original (english) man pages. Sometimes this is a straightforward typo, sometimes a hard to read sentence, sometimes this is a convention not held up and sometimes we simply do not understand the original. We use several distributions as sources and update regularly (at least every 2 month). This means we are fairly recent (some distributions like archlinux also update frequently) but might miss your latest upstream version once in a while, so the error might be already fixed. We apologize and ask you to close the issue immediately if this should be the case, but given the huge volume of projects and the very limited number of volunteers we are not able to double check each and every issue. Secondly we translators see the manpages in the neutral po format, i.e. converted and harmonized, but not the original source (be it man, groff, xml or other). So we cannot provide a true patch (where possible), but only an approximation which you need to convert into your source format. Finally the issues I'm reporting have accumulated over time and are not always discovered by me, so sometimes my description of the problem my be a bit limited - do not hesitate to ask so we can clarify them. I'm now reporting the issues for your project. If future reports should use another channel, please let me know. [1] https://manpages-l10n-team.pages.debian.net/manpages-l10n/ Man page: cron.8 Issue: B<systemd> → B<systemd>(1) "B<cron> is directly invoked by B<systemd> on entering multi-user " "runlevels\\&." -- Man page: cron.8 Issue: cron → B<cron> "Include the FQDN in the subject when sending mails\\&. By default, cron will " "abbreviate the hostname\\&." "Tell cron what to log about I<jobs> (errors are logged regardless of this " "value) as the sum of the following values:" "Tell cron to be more verbose and output debugging information; debugflags is " "the sum of those values:" "This does I<NOT> affect the environment of tasks running under cron\\&. For " "more information on how to modify the environment of tasks, consult " "B<crontab>(5)\\&." "The environment can be redefined in user\\*(Aqs crontab definitions but cron " "will only handle tasks in a single timezone\\&." "Debian introduces some changes to cron that were not originally available " "upstream\\&. The most significant changes introduced are:" -- Man page: cron.8 Issue: levels → I<loglevel> "The default is to log the start of all jobs (1)\\&. Logging will be disabled " "if levels is set to zero (0)\\&. A value of fifteen (15) will select all " "options\\&." -- Man page: cron.8 Issue 1: /var/spool/cron/crontabs → I</var/spool/cron/crontabs> Issue 2: B<crontab> → B<crontab>(1) "B<cron> searches its spool area (/var/spool/cron/crontabs/) for crontab " "files (which are named after accounts in /etc/passwd); crontabs found are " "loaded into memory\\&. Note that crontabs in this directory should not be " "accessed directly - the B<crontab> command should be used to access and " "update them\\&." -- Man page: cron.8 Issue 1: /etc/crontab → I</etc/crontab> Issue 2: /etc/cron\\&.hourly> → I</etc/cron\\&.hourly> Issue 3: /etc/cron\\&.daily → I<I</etc/cron\\&.daily> Issue 4: /etc/cron\\&.weekly → I</etc/cron\\&.weekly> Issue 5: /etc/cron\\&.monthly → I</etc/cron\\&.monthly> "B<cron> also reads /etc/crontab, which is in a slightly different format " "(see B<crontab>(5))\\&. In Debian, the content of /etc/crontab is predefined " "to run programs under /etc/cron\\&.hourly, /etc/cron\\&.daily, /etc/" "cron\\&.weekly and /etc/cron\\&.monthly\\&. This configuration is specific " "to Debian, see the note under DEBIAN SPECIFIC below\\&." -- Man page: cron.8 Issue 1: /etc/cron\\&.d → I</etc/cron\\&.d> Issue 2: /etc/crontab → I</etc/crontab> Issue 3: Markup of DEBIAN SPECIFIC is inconsistent, here in I<>, previously without? "Additionally, in Debian, B<cron> reads the files in the /etc/cron\\&.d " "directory\\&. B<cron> treats the files in /etc/cron\\&.d as in the same way " "as the /etc/crontab file (they follow the special format of that file, " "i\\&.e\\&. they include the I<user> field)\\&. However, they are independent " "of /etc/crontab: they do not, for example, inherit environment variable " "settings from it\\&. This change is specific to Debian see the note under " "I<DEBIAN SPECIFIC> below\\&." -- Man page: cron.8 Issue 1: /etc/crontab → I</etc/crontab> Issue 2: /etc/cron\\&.d → I</etc/cron\\&.d> "Like /etc/crontab, the files in the /etc/cron\\&.d directory are monitored " "for changes\\&. The system administrator may create cron jobs in /etc/" "cron\\&.d/ with file names like \"local\" or \"local-foo\"\\&." -- Man page: cron.8 Issue: All file names in I<> "/etc/crontab and the files in /etc/cron\\&.d must be owned by root, and must " "not be group- or other-writable\\&. In contrast to the spool area, the files " "under /etc/cron\\&.d or the files under /etc/cron\\&.hourly, /etc/" "cron\\&.daily, /etc/cron\\&.weekly and /etc/cron\\&.monthly may also be " "symlinks, provided that both the symlink and the file it points to are owned " "by root\\&. The files under /etc/cron\\&.d do not need to be executable, " "while the files under /etc/cron\\&.hourly, /etc/cron\\&.daily, /etc/" "cron\\&.weekly and /etc/cron\\&.monthly do, as they are run by run-parts " "(see B<run-parts>(8) for more information)\\&." "Support for /etc/cron\\&.{hourly,daily,weekly,monthly} via/etc/crontab," "The intended purpose of this feature is to allow packages that require finer " "control of their scheduling than the /etc/cron\\&." "{hourly,daily,weekly,monthly} directories to add a crontab file to /etc/" "cron\\&.d\\&. Such files should be named after the package that supplies " "them\\&." -- Man page: cron.8 Issue 1: ps → B<ps>(1) Issue 2: Maybe markup MAILFROM / MAILTO in B<>? "B<cron> then wakes up every minute, examining all stored crontabs, checking " "each command to see if it should be run in the current minute\\&. When " "executing commands, any output is mailed to the owner of the crontab (or to " "the user named in the MAILTO environment variable in the crontab, if such " "exists) from the owner of the crontab (or from the email address given in " "the MAILFROM environment variable in the crontab, if such exists)\\&. The " "children copies of cron running these processes have their name coerced to " "uppercase, as will be seen in the syslog and ps output\\&." -- Man page: cron.8 Issue: /etc/crontab → I</etc/crontab> "Additionally, B<cron> checks each minute to see if its spool " "directory\\*(Aqs modtime (or the modtime on the /etc/crontab file) has " "changed, and if it has, B<cron> will then examine the modtime on all " "crontabs and reload those which have changed\\&. Thus B<cron> need not be " "restarted whenever a crontab file is modified\\&. Note that the " "B<crontab>(1) command updates the modtime of the spool directory whenever " "it changes a crontab\\&." -- Man page: cron.8 Issue: Use B<> for name of environment variables? "If configured in I</etc/default/cron> in Debian systems, the B<cron> daemon " "localisation settings environment can be managed through the use of I</etc/" "environment> or through the use of I</etc/default/locale> with values from " "the latter overriding values from the former\\&. These files are read and " "they will be used to setup the LANG, LC_ALL, and LC_CTYPE environment " "variables\\&. These variables are then used to set the charset of mails, " "which defaults to \\*(AqC\\*(Aq\\&." -- Man page: cron.8 Issue: /etc/cron\\&.d → I</etc/cron\\&.d> "Support for /etc/cron\\&.d (drop-in dir for package crontabs)," -- Man page: cron.8 Issue 1: Filenames in I<> Issue 2: B<run-parts> → B<run-parts>(8) Issue 3: B<anacron> → B<anacron>(8) "Support for /etc/cron\\&.hourly, /etc/cron\\&.daily, /etc/cron\\&.weekly " "and /etc/cron\\&.monthly is provided in Debian through the default setting " "of the /etc/crontab file (see the system-wide example in B<crontab>(5))\\&. " "The default system-wide crontab contains four tasks: run every hour, every " "day, every week and every month\\&. Each of these tasks will execute B<run-" "parts> providing each one of the directories as an argument\\&. These tasks " "are disabled if B<anacron> is installed (except for the hourly task) to " "prevent conflicts between both daemons\\&." -- Man page: cron.8 Issue 1: B<run-parts> → B<run-parts>(8) Issue 2: cron → B<cron> Issue 3: /etc/cron\\&.d/ → I</etc/cron\\&.d/> "As described above, the files under these directories have to pass some " "sanity checks including the following: be executable, be owned by root, not " "be writable by group or other and, if symlinks, point to files owned by " "root\\&. Additionally, the file names must conform to the filename " "requirements of B<run-parts>: they must be entirely made up of letters, " "digits and can only contain the special signs underscores (\\*(Aq_\\*(Aq) " "and hyphens (\\*(Aq-\\*(Aq)\\&. Any file that does not conform to these " "requirements will not be executed by B<run-parts>\\&. For example, any file " "containing dots will be ignored\\&. This is done to prevent cron from " "running any of the files that are left by the Debian package management " "system when handling files in /etc/cron\\&.d/ as configuration files " "(i\\&.e\\&. files ending in \\&.dpkg-dist, \\&.dpkg-orig, \\&.dpkg-old, and " "\\&.dpkg-new)\\&." -- Man page: cron.8 Issue 1: /etc/cron\\&.d → I</etc/cron\\&.d> Issue 2: /etc/crontab → I</etc/crontab> Issue 3: cron → B<cron> "Support for /etc/cron\\&.d is included in the B<cron> daemon itself, which " "handles this location as the system-wide crontab spool\\&. This directory " "can contain any file defining tasks following the format used in /etc/" "crontab, i\\&.e\\&. unlike the user cron spool, these files must provide the " "username to run the task as in the task definition\\&." -- Man page: cron.8 Issue 1: B<run-parts>(8) : → B<run-parts>(8): Issue 2: /etc/crontab → I</etc/crontab> Issue 3: I<-l> → B<-l> Issue 4: /etc/default/cron → I</etc/default/cron> "Files in this directory have to be owned by root, do not need to be " "executable (they are configuration files, just like /etc/crontab) and must " "conform to the same naming convention as used by B<run-parts>(8) : they " "must consist solely of upper- and lower-case letters, digits, underscores, " "and hyphens\\&. This means that they I<cannot> contain any dots\\&. If the " "I<-l> option is specified to B<cron> (this option can be setup through /etc/" "default/cron, see below), then they must conform to the LSB namespace " "specification, exactly as in the I<--lsbsysinit> option in B<run-parts>\\&." -- Man page: cron.8 Issue 1: /etc/default/cron → I</etc/default/cron> Issue 2: /etc/cron\\&.d → I</etc/cron\\&.d> "Also, the default configuration of B<cron> is controlled by /etc/default/" "cron which is read by the init\\&.d script that launches the B<cron> " "daemon\\&. This file determines whether cron will read the system\\*(Aqs " "environment variables and makes it possible to add additional options to the " "B<cron> program before it is executed, either to configure its logging or to " "define how it will treat the files under /etc/cron\\&.d\\&." -- Man page: cron.8 Issue: /usr/share/doc/cron/copyright → I</usr/share/doc/cron/copyright> "Since year 1994, many modifications were made in this manpage, authored by " "Debian Developers which maintained cron; above is a short list, more " "information can be found in the file /usr/share/doc/cron/copyright\\&." -- Man page: crontab.1 Issue: configura\\(hy tion → configuration "If neither of these files exists, then depending on site-dependent " "configura\\(hy tion parameters, only the super user will be allowed to use " "this command, or all users will be able to use this command\\&." -- Man page: crontab.1 Issue: I<-h> → B<-h> "If the I<-h> option is given, B<crontab> shows a help message and quits " "immediately\\&." -- Man page: crontab.1 Issue: confuse crontab → confuse B<crontab> "If the 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, B<crontab> examines \"your\" crontab, i\\&.e\\&., the " "crontab of the person executing the command\\&. Note that B<su>(8) can " "confuse crontab and that if you are running inside of B<su>(8) you should " "always use the I<-u> option for safety\\*(Aqs sake\\&." "The I<-l> option causes the current crontab to be displayed on standard " "output\\&. See the note under the section called \\(lqDEBIAN SPECIFIC\\(rq " "below\\&." -- Man page: crontab.1 Issue 1: I<-h> → B<-h> Issue 2: crontab examines → B<crontab> examines "If the I<-n> option is given, it means \"dry run\": crontab examines " "\"your\" crontab for its syntax, and outputs a success message if this " "syntax is correct, but nothing is written to any crontab\\&." -- Man page: crontab.1 Issue: I<-r> → B<-r> "The I<-r> option causes the current crontab to be removed\\&." -- Man page: crontab.1 Issue 1: I<-e> → B<-e> Issue 2: B<sensible-editor> → B<sensible-editor>(1) "The I<-e> option is used to edit the current crontab using B<sensible-" "editor>\\&. After you exit from the editor, the modified crontab will be " "installed automatically\\&." -- Man page: crontab.1 Issue: Is -L (capital l) correct here? "HIGHLIGHTING THE OUTPUT OF CRONTAB -L" -- Man page: crontab.1 Issue 1: B<bat>() → B<bat> Issue 2: B<batcat> → B<batcat>(1) "One can also colourise this text with the program B<batcat> provided by the " "package B<bat>(), here is an example:" -- Man page: crontab.1 Issue: B<cron> → B<cron>(8) "The files I</etc/cron\\&.allow> and I</etc/cron\\&.deny> if they exist, must " "be either world-readable, or readable by group ``crontab\\*(Aq\\*(Aq\\&. If " "they are not, then B<cron> will deny access to all users until the " "permissions are fixed\\&." "B<cron> requires that each entry in a crontab end in a newline character\\&. " "If the last entry in a crontab is missing the newline, B<cron> will consider " "the crontab (at least partially) broken and refuse to install it\\&." -- Man page: crontab.1 Issue: Filename not in italic? "/var/spool/cron/crontabs" -- Man page: crontab.1 Issue: /var/spool/cron/crontabs → I</var/spool/cron/crontabs> "There is one file for each user\\*(Aqs crontab under the /var/spool/cron/" "crontabs 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 ``crontab\\*(Aq\\*(Aq group and configuring B<crontab> command with the " "setgid bid set for that specific group\\&." -- Man page: crontab.1 Issue: /usr/share/doc/cron/copyright → I</usr/share/doc/cron/copyright> "Since year 1994, many modifications were made in this manpage, authored by " "Debian Developers which maintained cron; above is a short list, more " "information can be found in the file /usr/share/doc/cron/copyright\\&." -- Man page: crontab.5 Issue: Colon at the end "will not work as you might expect\\&. And neither will this work" -- Man page: crontab.5 Issue 1: LOGNAME → I<LOGNAME> Issue 2: Markup for environment variables, e.g. I<>? Issue 3: /usr/bin/sh → I</usr/bin/sh> (B<> for command?) The latter is used below Issue 4: /etc/passwd → I</etc/passwd> "Several environment variables are set up automatically by the B<cron>(8) " "daemon\\&. SHELL is set to /usr/bin/sh, and LOGNAME and HOME are set from " "the /etc/passwd line of the crontab\\*(Aqs owner\\&. HOME and SHELL may be " "overridden by settings in the crontab; LOGNAME may not\\&." -- Man page: crontab.5 Issue: Markup for environment variables, e.g. I<>? "In addition to LOGNAME, HOME, and SHELL, B<cron>(8) will look at MAILTO if " "it has any reason to send mail as a result of running commands in \\(lqthis\\" "(rq crontab\\&. If MAILTO is defined (and non-empty), mail is sent to the " "user so named\\&. If MAILTO is defined but empty (MAILTO=\"\"), no mail will " "be sent\\&. Otherwise mail is sent to the owner of the crontab\\&. This " "option is useful if you decide on B</usr/bin/mail> instead of B</usr/lib/" "sendmail> as your mailer when you install cron -- B</usr/bin/mail> " "doesn\\*(Aqt do aliasing, and UUCP usually doesn\\*(Aqt read its mail\\&." -- Man page: crontab.5 Issue: /etc/crontab → I</etc/crontab> "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 (\\*(Aq\\en\\*(Aq)" "\\&. 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 998 characters\\&." "The following lists the content of a regular system-wide crontab file\\&. " "Unlike a user\\*(Aqs crontab, this file has the username field, as used by /" "etc/crontab\\&." -- Man page: crontab.5 Issue 1: Markup for environment variables, e.g. I<>? Issue 2: charac\\(hy ters → characters "The \\(lqsixth\\(rq field (the rest of the line) specifies the command to be " "run\\&. The entire command portion of the line, up to a newline or % " "character, will be executed by B</usr/bin/sh> or by the shell specified in " "the SHELL variable of the cronfile\\&. Percent-signs (%) in the command, " "unless escaped with backslash (\\e), will be changed into newline charac\\" "(hy ters, and all data after the first % will be sent to the command as " "standard input\\&." -- Man page: crontab.5 Issue: /etc/rc → I</etc/rc> "Environment variables can be set in the crontab\\&. In BSD or AT&T, the " "environment handed to child processes is basically the one from /etc/rc\\&." -- Man page: crontab.5 Issue: them\\(hy selves → themselves "The B<cron> daemon runs with a defined timezone\\&. It currently does not " "support per-user timezones\\&. All the tasks: system\\*(Aqs and user\\*(Aqs " "will be run based on the configured timezone\\&. Even if a user specifies " "the I<TZ> environment variable in his crontab this will affect only the " "commands executed in the crontab, not the execution of the crontab tasks " "them\\(hy selves\\&. If one wants to specify a particular timezone for " "crontab tasks, one may check the date in the child script, for example:" -- Man page: crontab.5 Issue: I<crontab> → B<crontab> "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 weekday of a month\\&. To have a task run in a time period that " "cannot be defined using I<crontab> syntax, the best approach would be to " "have the program itself check the date and time information and continue " "execution only if the period matches the desired one\\&." -- Man page: crontab.5 Issue: I<ncal> or I<calendar> For → B<ncal>(1) or B<calendar>(1). For "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 I<ncal> " "or I<calendar>\\&. For example, to run a program the last Saturday of every " "month you could use the following wrapper code:" -- Man page: crontab.5 Issue: /usr/share/doc/cron/copyright → I</usr/share/doc/cron/copyright> "Since year 1994, many modifications were made in this manpage, authored by " "Debian Developers which maintained cron; above is a short list, more " "information can be found in the file /usr/share/doc/cron/copyright\\&." -- Dr. Helge Kreutzmann deb...@helgefjell.de Dipl.-Phys. http://www.helgefjell.de/debian.php 64bit GNU powered gpg signed mail preferred Help keep free software "libre": http://www.ffii.de/
signature.asc
Description: PGP signature
