Package: apache2 Version: 2.2.22-13+deb7u1 Severity: wishlist Dear Maintainer,
When Apache is upgraded I see more downtime then needed. At the start of a package upgrade the Apache daemon is stopped. ... Work is done on other packages ... e.g. rebuilding kernel stuff ... Apache configure/post install scripts fire ... Apache is started again. When a kernel upgrade is done at the same time this downtime can easily last more then a minute. Is there a way for Apache to pull stopping and starting closer together? I've experimented by adding 'return 0' to apache_wait_stop() in /etc/init.d/apache2. And restarting Apache by hand afterwards. Which seems to upgrade just fine. Bind is an example of a service that is only restarted at the end of an upgrade. It's not a huge issue, but it would make such updates less intrusive. -- System Information: Debian Release: 7.4 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 3.2.0-4-686-pae (SMP w/1 CPU core) Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash -- Met vriendelijke groet / Regards, Herman van Rink Initfour websolutions -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
