On Sat, Feb 19, 2011 at 06:07:06PM -0800, Josh Triplett wrote: > On Sat, Feb 19, 2011 at 04:55:16PM -0800, Steve Langasek wrote: > > On Sat, Feb 19, 2011 at 04:17:00PM -0800, Josh Triplett wrote: > > > - Both libc6 and libpam0g prompted to restart services, causing them to > > > get restarted twice in the same upgrade. > > Not a bug. Each of these libraries need to make sure services are restarted > > for compatibility with their own set of dynamically loadable plugins on the > > system. Thus, to keep the services operational during the upgrade, the > > affected services must be restarted after unpack of *each* of the libraries > > in question. > The net result still feels less than impressive, regardless of the > technical reasons behind the two separate prompts and restarts. > Thinking beyond the bounds of just what a maintainer script can do, can > you think of any technical solution to avoid one or both of these > restarts? Sure, you can stop all services on your system before you upgrade. The services in question will be unusable from the time the modules in question are unpacked on the system (nss modules and pam modules, respectively) and will only be usable again once they've been restarted. An arbitrary subset of these services may be critical to the system (and may even be critical for the admin's access to the system during the upgrade), so this window needs to be kept as small as possible (0 in the case of libpam, and between libc unpack and libc configure in the case of libc). -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer http://www.debian.org/ slangasek@ubuntu.com vorlon@debian.org
Attachment:
signature.asc
Description: Digital signature