What I'd like to do is just leave this bug report open for now so other
possibly affected users can see it, and fix after Squeeze. This change
has also been present in Ubuntu since 10.10 and nobody noticed so far,
so I guess the impact on users upgrading from Lenny - Squeeze should be
Package: cron
Version: 3.0pl1-116
Severity: minor
--- Please enter the report below this line. ---
After upgrade from cron 3.0pl1-114 to 3.0pl1-116 I had the following
problem:
My log reporting system began to send me a lot of error messages from cron.
Digging down it appears that the following
tag 608874 confirmed
thanks
Hi Philippe,
On 01/04/2011 10:08 AM, Philippe Teuwen wrote:
After upgrade from cron 3.0pl1-114 to 3.0pl1-116 I had the following
problem:
I can confirm the general issue, however this should have first appeared
in -110, not -114 (see #581612, where we accidentally
After upgrade from cron 3.0pl1-114 to 3.0pl1-116 I had the following
problem:
I can confirm the general issue, however this should have first appeared
in -110, not -114 (see #581612, where we accidentally sent mails on exit
!= 0, which we fixed in -112).
Could you check your logs and
On 01/04/2011 08:38 PM, Philippe Teuwen wrote:
You're right that the problem was introduced earlier.
I guess I saw it only after this upgrade because of an upgrade of
logcheck as well and now logcheck reports me that error from
/var/log/syslog.
Ah, so it is also visible in the default
5 matches
Mail list logo
