Your message dated Sat, 09 Aug 2014 21:34:26 +0000
with message-id <[email protected]>
and subject line Bug#756047: fixed in cron 3.0pl1-124.2
has caused the Debian Bug report #756047,
regarding cron.service: ignores SIGPIPE
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 [email protected]
immediately.)
--
756047: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756047
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: cron
Version: 3.0pl1-124.1
systemd was forced on me yesterday - and while it took me 4 hours to
get system back to boot (that's another story), I thought it is
reasonably stable to survive during night.
But today when I came to work, I found that my system crashed due to
/tmp being full. Investigation revealed that under systemd cron - and
everything spawned by cron - ignores SIGPIPE. So cron script doing:
while true; do echo "X=`getRandomNumber`"; done | process10NumbersAndQuit
now emits gazillion of:
renew.sh: line 5: echo: write error: Broken pipe
and never stops, which end up in /tmp in file where cron redirected stderr...
Can you ensure that cron scripts are run in same environment under
sysvinit and systemd? I know this script got broken in quite fatal
way, but I have hundreds of other, and I did not find any cron option
to not ignore SIGPIPE when starting children, and in shell it seems
impossible to revert SIGPIPE to default handling if it was ignored
when shell started. For now I've changed systemd to use cron's
initscript rather than cron.service - that seems to do the trick.
You can check it by creating script:
while true; do echo x; done | head -1
When run under sysvinit started cron, it nicely stops after printing
one 'x'. Under systemd started cron it generates infinite amount of
stuff on stderr.
Thanks, Petr
--- End Message ---
--- Begin Message ---
Source: cron
Source-Version: 3.0pl1-124.2
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 [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Ansgar Burchardt <[email protected]> (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 [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Mon, 04 Aug 2014 21:44:00 +0200
Source: cron
Binary: cron
Architecture: source
Version: 3.0pl1-124.2
Distribution: unstable
Urgency: medium
Maintainer: Javier Fernández-Sanguino Peña <[email protected]>
Changed-By: Ansgar Burchardt <[email protected]>
Description:
cron - process scheduling daemon
Closes: 756047
Changes:
cron (3.0pl1-124.2) unstable; urgency=medium
.
* Non-maintainer upload.
* debian/cron.service: Set IgnoreSIGPIPE=false. (Closes: #756047)
* debian/cron.service: Add Documentation field.
Checksums-Sha1:
e9524b2aa50d8bd99a9a98ae3db82182d1ec4198 1927 cron_3.0pl1-124.2.dsc
182e2cdd93155211eaf6d2c5fe3db0ecdce0464a 97035 cron_3.0pl1-124.2.diff.gz
Checksums-Sha256:
2b046803b188e668df1e822aa072a38b27de23e779e8c3edd44caa4c2a4c20eb 1927
cron_3.0pl1-124.2.dsc
df9aede5d80c9589aa46bfad276b3116d2fdd1bd6290ca1abdd70ab4aab146cc 97035
cron_3.0pl1-124.2.diff.gz
Files:
241170d31d502435bf80d913189512e4 1927 admin important cron_3.0pl1-124.2.dsc
d0a01af92950f855e8959fd5e8ee6066 97035 admin important
cron_3.0pl1-124.2.diff.gz
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQIcBAEBCgAGBQJT3+ZdAAoJEIATJTTdNH3IYsAP/1HH+EmnEp7WgoVYF7bXT802
gNRJUt3ug3WP2hguguRBM9PHk8YpT10KsyaSKscrmCIMSX6nLPS22LboNNgac2S2
TMLS3zNK6GtiWdvpw9QQJUe9ZFy39ILffodwNX5I7QIBrb1cqptSYRLFlQDt/JoJ
6mWH+zuCTgmL8ptlASo2KBfjqsC6+l9H9PN/I+4CkM38Beydy1GhlXi4nh9WWuJ9
x20sn3F/FuW50+Nd9NFEbKfzJZ08ATxkzY/jonbHXS1/tLO3I6qA2UKg/DfRiTH7
2aQID2RhnpzRDOV3Vy8iVOv07LOGuquLgISOc531FKvYQtdULow/1ZzH/2MajuSj
IcGAzc+W2Ic2Dkc7MzjQA+emjQB2MRkEaDnawRUEqB59+MK6qJakCnNu+uHCtBD7
lFPvkSLoUFS62qNicyh4e0qfOru+eo0ZPmBkuAqBg5YqtgOz7UwkF9oWlkvkstqa
Rxnka0H6dxgP5FglZvMNtdAxoMSND1x3b8phoykt9w70CMEdGqSjFMiCYCLDMmOg
8MCvVT9hgctJotIG0A89X/aUpmHJq6P5wrUu8pAkkKIPTpgL1zpH0o82XkdyfLSu
rche2/4V6/kj0NBDt5gWhxGf7t9n6m+Je1SDgxXwQPtigzVDNC6/BqtkyKwBCKXh
p4qLRQ87TmLj6Goo5K73
=toQ+
-----END PGP SIGNATURE-----
--- End Message ---
