Quoting Michael Stapelberg (2013-05-11 22:48:05) > Jonas Smedegaard <[email protected]> writes: > > As subject says, kanla uses dummy account info by default, and the > > daemon is started by default. > So, thinking about it, why precisely is that a problem? > > I certainly agree that it is not very useful, but it is not harmful > either. The kanla process will run and try to connect without success, > until you set up your config file correctly.
I find it wrong (and from a privacy perspective unacceptable) to have a monitoring daemon by default also be a beacon towards the outside World. Since there is a simple alternative of providing _no_ credentials instead of _bogus_ credentials, I propose to do that. > > Perhaps a reasonable-yet-simple-to-implement middleground would be > > to comment out the dummy data from shipped config file, and have the > > init script gracefully fail (i.e. with a warning but exit 0) if > > account info is undefined. > Unfortunately, this seems to be rather hard to achieve. invoke-rc.d’s > exit code is handled as fatal in the postinst autoscript added by > dh_installinit and I really don’t want to make missing credentials a > non-fatal error in kanla. I later realized that seemingly the actual kanla code fails gracefully if it cannot connect initially. If that is correctly understood, then how about doing first part (comment out credentials by default) and leave it to kanla to do second part (i.e. not mess with sysv script at all)? - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
