Your message dated Mon, 12 Mar 2018 23:49:37 +0000
with message-id <e1evxcd-000hg2...@fasolo.debian.org>
and subject line Bug#792572: fixed in cron 3.0pl1-130
has caused the Debian Bug report #792572,
regarding cron: Some improvements for crontab.5
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
792572: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=792572
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cron
Version: 3.0pl1-127
Severity: minor
Tags: patch
Dear Maintainer,
Here are three small patches for the crontab.5 manpage.
The third, fixing the example, was mostly prompted by the mixed "`... $( ... )
...`"
usage, but also because it's more complicated than it need be, so dificult to
understand.
Cheers, Phil.
>From c9f07c7ab4e06631ca6b280b663ef004685a2e31 Mon Sep 17 00:00:00 2001
From: Philip Hands <p...@hands.com>
Date: Thu, 16 Jul 2015 10:25:16 +0100
Subject: [PATCH 1/3] general typos
---
crontab.5 | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/crontab.5 b/crontab.5
index 66ba2e4..5f79f8e 100644
--- a/crontab.5
+++ b/crontab.5
@@ -71,7 +71,7 @@ will not work as you might expect. And neither will this work
B=2
C=$A $B
.PP
-There will not be any subsitution for the defined variables in the
+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
@@ -121,7 +121,7 @@ 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 - ie. either the default system locale, if no LC_* environment
+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
( see
.IR locale (7) ).
@@ -265,7 +265,7 @@ MAILTO=paul
.fi
.SH EXAMPLE SYSTEM CRON FILE
-The following lists the content of a regular system-wide crontab file. Unlinke 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
@@ -327,7 +327,7 @@ image off. For example, it is not straightforward to define the last
weekday of a month. If a task needs to be run in a specific period of time
that cannot be defined in the
.I crontab
-syntaxs the best approach would be to have the program itself check the
+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.
@@ -346,7 +346,7 @@ the following wrapper code:
.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 (ie, terminated by EOF), cron will
+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.
--
2.1.4
>From a3318cde1257d6559d15c034f036bed653f8ee3b Mon Sep 17 00:00:00 2001
From: Philip Hands <p...@hands.com>
Date: Thu, 16 Jul 2015 10:25:51 +0100
Subject: [PATCH 2/3] fixup wording about syntax limitations
---
crontab.5 | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/crontab.5 b/crontab.5
index 5f79f8e..ede9881 100644
--- a/crontab.5
+++ b/crontab.5
@@ -322,10 +322,10 @@ of the crontab tasks themselves.
The
.I crontab
-syntax does not make it possible to define all possible periods one could
-image off. For example, it is not straightforward to define the last
-weekday of a month. If a task needs to be run in a specific period of time
-that cannot be defined in the
+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
--
2.1.4
>From c4652d27df7bb4a7557f245925b9948a5931e744 Mon Sep 17 00:00:00 2001
From: Philip Hands <p...@hands.com>
Date: Thu, 16 Jul 2015 11:27:46 +0100
Subject: [PATCH 3/3] make "Last Saturday" example less twisted
---
crontab.5 | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/crontab.5 b/crontab.5
index ede9881..363c3c5 100644
--- a/crontab.5
+++ b/crontab.5
@@ -340,7 +340,7 @@ 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)" = "`ncal | grep $(date +\\%a | sed \-e 's/.$//') | sed \-e 's/^.*\\s\\([0-9]\\+\\)\\s*$/\\1/'`" ] && echo "Last Saturday" && program_to_run
+0 4 * * Sat [ "$(date +\\%e)" = "$(LANG=C ncal | sed -n 's/^Sa .* \\([0-9]\\+\\) *$/\\1/p')" ] && echo "Last Saturday" && program_to_run
.fi
--
2.1.4
--- End Message ---
--- Begin Message ---
Source: cron
Source-Version: 3.0pl1-130
We believe that the bug you reported is fixed in the latest version of
cron, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 792...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Javier Fernández-Sanguino Peña <j...@debian.org> (supplier of updated cron
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Mon, 12 Mar 2018 22:00:01 +0100
Source: cron
Binary: cron
Architecture: source i386
Version: 3.0pl1-130
Distribution: unstable
Urgency: medium
Maintainer: Javier Fernández-Sanguino Peña <j...@debian.org>
Changed-By: Javier Fernández-Sanguino Peña <j...@debian.org>
Description:
cron - process scheduling daemon
Closes: 705570 757191 767016 783665 792572 801384 834728 840601 892720 892721
892724
Changes:
cron (3.0pl1-130) unstable; urgency=medium
.
* debian/postinst: Do not do check if /var/spool/cron/crontabs if empty
(Closes: 892720, 892721, 892724)
* debian/cron.service:
- Add dependency on nss-user-lookup.target in the definition which
properly fixes the issues when cron is started before centralised user
repositories are available (e.g. LDAP or Active Directory). This
should avoid errors in syslog similar to the following:
"crond[PID]: (CRON) bad username (/etc/cron.d/JOBNAME)"
(Closes: #767016, #801384, #783665) (LP: #1593317)
- Also remove Type=idle change added in previous upload, which was not
the correct fix to apply.
- Add automatic restart on failure (Closes: #834728)
* debian/cron.init: Revert previous change - instead of adding $all, add sssd
to the services that should be started/stopped before/after cron.
* crontab.5:
- Add improvements and fixes to manpage provided by Philip Hands
(Closes: #792572)
- Document that system wide defaults run from 6 am to 7 am.
(Closes: #757191)
- Document how asterisks are processed in dom and dow fields using
patch provided by Christian Pekeler (Closes: #840601)
Also see https://treats.wdt.io/cron-bug.html
* debian/crontab.main, crontab.5: Add documentation comments similarly as to
how Fedora / Red Hat Enterprise Linux documents (crontab package). This
comments more descriptive and provides inexperienced users with a better
understanding of the syntax. (Closes: #705570)
Checksums-Sha1:
83bb41c481079ab385f1e84754df3bc81c3668a2 1926 cron_3.0pl1-130.dsc
06140002dc756895725c8796d3ed111f1c1d4890 101197 cron_3.0pl1-130.diff.gz
037da9f11a51eb458f263e6bf99cd67557f5ddd8 78772 cron-dbgsym_3.0pl1-130_i386.deb
98dc43e253e173f54ede0a7ec14b6cda51dd6237 6329 cron_3.0pl1-130_i386.buildinfo
d21ef5105c6f1e53ed53df1c853cf3f862e5dc98 99300 cron_3.0pl1-130_i386.deb
Checksums-Sha256:
3ef457bb1f1b4a2d574269d45a69dde499a490666517875586e96fe9138a73c1 1926
cron_3.0pl1-130.dsc
5a8ae124d5051db373157f996eba3f68d404b115ed3e3e4b9433a83a4bf413b9 101197
cron_3.0pl1-130.diff.gz
d35d615ada5a88bb45ab609baa5e57eaadb4f41131a3b4d602488d604a369d28 78772
cron-dbgsym_3.0pl1-130_i386.deb
9826d4e15f0f53832c24b8bbd6416a9b7d659e39e5690dfa991a93ee39be9c49 6329
cron_3.0pl1-130_i386.buildinfo
ad8501ab21d1e8e70f3f6ffe80803f4668057aa658686e7ddfd714052949b656 99300
cron_3.0pl1-130_i386.deb
Files:
4c859f3469075e9219d49f07e2ab242a 1926 admin important cron_3.0pl1-130.dsc
c32f7aa37249c706b008ebbe1c1bee35 101197 admin important cron_3.0pl1-130.diff.gz
6468a1bf91ae71d6ac5c5bacfcb5bf4b 78772 debug optional
cron-dbgsym_3.0pl1-130_i386.deb
25862b203eb7205047772975f1c58dcb 6329 admin important
cron_3.0pl1-130_i386.buildinfo
4b3458ce939dc746336048be3808f5ff 99300 admin important cron_3.0pl1-130_i386.deb
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEEFQ8Kq6ttIR3DT+AOix9vSKslf5gFAlqnBCEACgkQix9vSKsl
f5h78w/8D/kUAuzMFLV5MbeB6NjgAbyCdY4LtiL4qL+9mxASQAbPDr7pwtm82ERX
zliHRGebG/eSZvYcu/4Ewlt95uNGVYyr7QEOAh9foZergQUeNi7fGnRIi4El+8gs
ekESRFakCPAV6YqmKNsQC+WvTzCdSmqj4dD/L+ceYEr0q50qHPyN0fWiBWPYRAg/
ubLJ6GHazJIZA088uU4cJnUge5jPde59t0sUshvMLol8BlRuJVkX0QhleFfhEVVF
hlZYBXW6Kl2ANKwRRrw6Gb62uP9+dfZdbR6Po4tTSXfzfNA6mRghz4DNVQzAGToA
675BxEAIVF7m2If+cNCkneeL9hiLe/iGe77QfyxToI2f+JzoxQIgo1SqugfxJlIU
3zTCXxvSpGqV1A9AoW8kkY1Jwg4In3U3on9SCiIOzuOXYuD/4hrsLQR05hKu/ybD
EzsJeVgWIWUCZ1Vl+CC27ovaTu0RdKFTgbEj09JgXkfeXX5gGnk8UcsuK5Kme4ms
Ixauo6CgnAp14YrRMJPH22V3t7Ijx8mbpcgmnRvv9yyzn7gmmmwkwbMCYAHCp5F8
XwttcpH9toCKPWCdzimN4FOlVe52UcbzceIiZjM/JLf7DLnNh1AWHEd9Sd69Umm1
egCrMvNY9czwmeLXMWanyLF6S4xtL44wTWt+KacQ7bFnDyqQOK4=
=Z07i
-----END PGP SIGNATURE-----
--- End Message ---
