Your message dated Sat, 21 May 2016 23:40:00 +0200
with message-id <[email protected]>
and subject line Mark old fixed bug as 'done'
has caused the Debian Bug report #589679,
regarding smokeping: default configuration bigloss not recommended any more by
man page
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.)
--
589679: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=589679
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: smokeping
Version: 2.3.6-5
Severity: wishlist
Hi,
Debian's default configuration still defines an alert named bigloss
with a pattern "==0%,==0%,==0%,==0%,>0%,>0%,>0%". In all my setups,
this creates lots of alerts.
Upstream's man page doesn't define this bigloss alert any more. They
instead have an alert called lossdetect with a pattern
"==0%,==0%,==0%,==0%,>20%,>20%,>20%".
I guess this has been changed because of the lots of Alerts that
bigloss creates. Maybe it would be a good idea to apply upstream's
changes to Debian's default config.
Greetings
Marc
--- End Message ---
--- Begin Message ---
This bug was closed in 2011, but was only marked as 'fixed-in-versions',
not done. Let's close it to clean the BTS.
--
iustin
signature.asc
Description: PGP signature
--- End Message ---
