-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hello,
Am Mi den 10. Aug 2011 um 15:59 schrieb Christian Kastner:
On 08/10/2011 12:43 PM, Klaus Ethgen wrote:
The solution of #609780 breaks all log analysing tools.
First, it most certainly does not break all log analyzing tools. Most
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Package: cron
Version: 3.0pl1-119
Severity: normal
Tags: sid
The solution of #609780 breaks all log analysing tools. More over it
makes no sense to log the PID twice in the logs.
In logfiles the PID is expected direct behind the binary and is
On 08/10/2011 12:43 PM, Klaus Ethgen wrote:
The solution of #609780 breaks all log analysing tools.
First, it most certainly does not break all log analyzing tools. Most
notably, logcheck works fine with this solution. Please provide some
specific examples of such tools so that we may better
On Wed, Aug 10, 2011 at 11:43:28AM +0100, Klaus Ethgen wrote:
The solution of #609780 breaks all log analysing tools. More over it
makes no sense to log the PID twice in the logs.
Breaks all seems rather harsh (and untrue, we did review logcheck). Anyway,
if a log analysing tool breaks because
4 matches
Mail list logo
