Your message dated Sat, 2 Mar 2019 22:39:44 +0100 with message-id <[email protected]> and subject line Re: Bug#14238: dpkg: delayed configuration causes crashes and inaccessible systems has caused the Debian Bug report #14238, regarding Please add new tag to cause immediate configuration to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 14238: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=14238 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: dpkg Version: 1.4.0.19 Severity: critical This is an earlier post of me re delayed configuration on debian-devel: I am maintaining a couple of systems that I can just reach via telnet. Upgrading the system means that functionality is stopped in the unpacking phase of dpkg and not enabled until the configuration phase. That might take quite a while if a large number of packages is upgraded and can lead to severe problems with an internet server. If packages could be equipped with some sort of flag that would tell dpkg that this critical package needs to be configured immediately then this problem would be solved. Two variations come to my mind: 1. A package needs to be immediately configured after installation. 2. A package needs to be immediately configured if upgraded. Packages using this flag should not have any user interaction in the postinst script so that the upgrade process does not stop by dpkg invoking the postinst script. Typical candidates for such functionality are: netbase Shutting down netbase means disabling inetd,portmapper! No telnet access no ftp access during the dpkg session. If something goes wrong your system is dead. If you are across the country somewhere then good luck. netstd Will stop routed and NFS. Loosing routed will shut your server down after a few minutes because it wont be able to route packages to you anymore. nis Shutting down NIS will probably prevent anyone from connecting to your systems. Having NIS down for any extended amount of time is suicide for the system. libreadline* For the hamm upgrade having an unconfigured readline can make bash dysfunctional. bash Is critical to the system. Anything that would prevent from working for any time period must be avoided. ldso must work at all times. libraries It is unhealthy to have important libraries in a state where important system software is not able to run because it depends on those libraries. Server daemons might use the flag to restart the daemons immediately after an upgrade in order to minimize downtime. Upgrading an Internet Server while it is running in full operation becomes a real possibility. So far I have also upgraded my servers under full operation but I had to do it piece by piece by running dpkg -i on single .debs. The immediate configuration option might help the installation process to be more robust and improve the overall reliability of the Debian distribution. -- System Information Debian Release: 1.3 Kernel Version: Linux cyrix200 2.1.60 #20 Mon Oct 27 18:11:52 PST 1997 i486 unknown Versions of the packages dpkg depends on: libc6 Version: 2.0.5c-0.1 libg++272 Version: 2.7.2.8-0.1 ncurses3.4 Version: 1.9.9g-5
--- End Message ---
--- Begin Message ---Hi! On Wed, 1997-10-29 at 16:27:52 -0800, Christoph Lameter wrote: > Package: dpkg > Version: 1.4.0.19 > Severity: critical > I am maintaining a couple of systems that I can just reach via telnet. > Upgrading the system means that functionality is stopped in the unpacking > phase of dpkg and not enabled until the configuration phase. That might > take quite a while if a large number of packages is upgraded and can lead > to severe problems with an internet server. This is a local policy matter that can be fully controlled via policy-rc.d. > If packages could be equipped with some sort of flag that would tell dpkg > that this critical package needs to be configured immediately then this > problem would be solved. Two variations come to my mind: > > 1. A package needs to be immediately configured after installation. > 2. A package needs to be immediately configured if upgraded. > > Packages using this flag should not have any user interaction in the > postinst script so that the upgrade process does not stop by dpkg invoking > the postinst script. I'm not sure how that'd be accomplished, say, if there are conffiles involved and the admin has done local modifications. > Typical candidates for such functionality are: > > netbase Shutting down netbase means disabling inetd,portmapper! > No telnet access no ftp access during the dpkg session. If > something goes wrong your system is dead. If you are > across the country somewhere then good luck. policy-rc.d > netstd Will stop routed and NFS. Loosing routed will shut your > server down after a few minutes because it wont be able > to route packages to you anymore. Ditto. > nis Shutting down NIS will probably prevent anyone > from connecting to your systems. Having NIS down > for any extended amount of time is suicide for the > system. Ditto. > libreadline* For the hamm upgrade having an unconfigured readline > can make bash dysfunctional. Any shared library Pre-Depended by an Essential:yes package should be considered to have to obey the same requirements as the Essential:yes packages, so they do need to keep working even if not fully configured. > bash Is critical to the system. Anything that would prevent > from working for any time period must be avoided. Ditto Essential:yes rationale. > ldso must work at all times. Ditto. > libraries It is unhealthy to have important libraries in a state > where important system software is not able to run because > it depends on those libraries. This depends on their users. > Server daemons might use the flag to restart the daemons immediately after > an upgrade in order to minimize downtime. Upgrading an Internet Server > while it is running in full operation becomes a real possibility. > > So far I have also upgraded my servers under full operation but I had to > do it piece by piece by running dpkg -i on single .debs. > > The immediate configuration option might help the installation process to > be more robust and improve the overall reliability of the Debian > distribution. I think this request is already handled by other means and guarantees, and I don't think we need what is proposed here. I'm thus closing it. Thanks, Guillem
--- End Message ---
