Package: needrestart Version: 2.1-1 Severity: wishlist
Hi. There should be "powerful" notification methods for the results of needrestart and checking/notification shouldn't just happen when apt is run, as the admin may forget to take care on the results then or packages may be installed in batch mode or via dpkg and needrestart not run at all. I don't think that needrestart should get an arbitrary list of notification methods, i.e. there's no need to code a mail sending plugin or something like that. Why? IMHO there are basically two cases, larger clusters or collection of nodes and single (e.g. desktop) nodes. For the former, people should be delegated to use proper monitoring systems (e.g. Nagios/Icinga, see bug #787294, which already provide countless of notification ways from email over XMPP to SMS) and which also already provide full control over when/how often the current status should be checked. In other words, I don't think it's needrestart's job to re-create anything of this on it's own, when there already tools out for this. For single (e.g. desktop) nodes it's however unreasonable to run something like Nagios/Icinga. For these, a configurable cron job would be nice that periodically re-checks (and of course also notifies). What should be configurable? - whether it runs at all (cause people checking via e.g. Nagios/Icinga likely want to disable this) - when/how often it runs - what it should check/report here I'd basically expect the same options as I've listed in #787294 Cheers, Chris. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
