On 10/29/18 10:13 PM, Faidon Liambotis wrote: > On Mon, Oct 29, 2018 at 09:10:40PM +0100, Sebastiaan Couwenberg wrote: >>> I disagree on that -- excessive and spurious logging is a serious issue >>> and filling up logs of the Nagios server fast is as well. Logrotate >>> helps, but not with that rate, and regardless, not a great solution >>> either (the logs become just an endless sea of garbage). >> >> Then we'll have to agree to disagree. As maintainer of the package I >> have evaluated the severity of this issue, and not deemed it high enough >> to be eligible for a stable update. >> >>> And really, what's the downside? These logs are useless; the patch is >>> upstream, is tiny, safe and easily backportable. If you're concerned >>> about the effort... I'd be happy to provide patches and/or NMU! >> >> If you're going to the effort to patch the package, why bother arguing >> in this issue? Just provide the package in your local repo and be done >> with it. > > We've already done that (in fact, before even reporting this bug!): > https://phabricator.wikimedia.org/T207775#4693987 > https://apt.wikimedia.org/wikimedia/pool/main/n/nagios-nrpe/ > > ...but, given that we encountered this, and we already battle-tested it, > we thought it might be preferrable for other Debian users to benefit > from the fix as well. Given the Nagios forum link above, it doesn't look > like we were the only ones affected. All of us in the Wikimedia team > (three of us DDs) in that loop agreed on this FWIW :)
But none of you are active in the Nagios team, (co-)maintainers of the nrpe package, nor SRMs. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
