Michael wrote on 2013-12-14: > The package cannot know which things to monitor and where to send > alerts to. There just is no way to have it in “normal working > condition” unless you configure it.
The apache2 package also cannot know which content to serve, so serves virtually nothing by default - but ready for adding content, not (as with kanla) spewing debug hints filling up the disk. I would find it more appropriate to include the "fail" plugin but have it commented out by default - same as you've done with a sample use of the "http" plugin. For a better user experience, you could add debconf handling of where to send alerts to, but that is unneeded for the issue of this bugreport. >> If one wants debugging output, onewould enable optional features for >> that, not expect it to be enabled by default. > I disagree. It is tempting and likely that without this message, > people would configure kanla, say “this looks about right” and never > get any alerts. Having a sightly annoying default configuration to err > on the side of caution is the right thing, IMO. If you consider it unsuitable for kanla to be provided in a state that works out-of-the-box (i.e. working very little as nothing is being monitored, but also no debugging is enabled), then have the daemon turned *off* initially. I strongly recommend *against* that, however, as then _other_ users who _do_ understand what silence means cannot automatically install a working kanla (e.g. by providing add-on monitoring snippets by another package). - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private
signature.asc
Description: signature
