Package: needrestart Version: 1.2-1 Severity: wishlist
Hi. I think needrestart should default to not restart services. This is especially important for servers, where restarting of daemons is typically not something that you do immediately after upgradeing packages or which often requires careful planning and downtimes. For many services of course, it's no problem to restart them immediately (e.g. ssh, irqbalance, ntp) but for others (e.g. postgresql, httpd) the above typically applies. Defaulting to yes may even cause troubles on desktops, where, right now, it's e.g. still a problem to restart gdm3 (see bug #762756). If something like #763936 is implemented, than defaulting to "no" should also cause not much issues, since it would be simple to change the values of all suggestions to "yes". On alternate solution in defaulting to "no" could be a "auto" mode in which a whitelist of services is maintained, for which it will default to restart, while for all others it will default not to restart. Such whitelist would contain services for which interruptions/restarts are typically no problem, e.g. - ssh (existing connections continue to live) - nameservers (each proper domain should have more than one NS) - ntp - irqbalance - etc. pp. Of course some services are in a grey zone like e.g.: - ejabberd while proper clients should basically reconnect immediately and while no messages should get lost, the reality is that basically no XMPP client/server correctly uses TCP to track whether messages got transmitted and resends them if necessary. Plus, users will at least notice the reconnect. Cheers, Chris. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
