Thijs Kinkhorst wrote: >> FWIW, I don't agree. I don't find it acceptable to have a >> fresh-installed package writing 2 lines on my syslog every 5 seconds. > > Busylooping is obviously wrong, but doing it every 5 seconds is not an > unacceptable burden. It does not load the system significantly. Especially > because you will be using puppetca not long after installing the package > to authorise the host and the message will go away. It's not like this > behaviour occurs permanently, rather it will only be in the bootstrapping > window between installing puppet on a host and acknowledging it on the > puppetmaster. You're assuming that you are prepared to deploy puppet.
Sometimes people just install a package to read documentation/the manpages/read the code etc. It should either need manual work for the init script to start (i.e. disable autostart) or have a sensible default for the loop delay. I think that the first would hurt automated installations, esp. if it isn't a debconf question that can be preseeded. Therefore, I'd suggest just increasing the delay to the upstream default. > I do not contest that such a change could be useful but the package is in > my opinion in a condition to release. Well, I'd say that I think it'd be acceptable to have such a change such late in the release cycle but I wouldn't suggest removing the package if this isn't fixed. In any case, I'd prefer it if the maintainer was a little more responsive... Regards, Faidon -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
