clone 234106 -1 retitle -1 runit: fails to install in vserver environment submitter -1 [EMAIL PROTECTED] quit
Hi Gilles, sorry I missed your previous mail; now this issue is a separate bug report. On Mon, Apr 25, 2005 at 01:28:02AM +0200, Gilles wrote: > The actual problem lies with the call: > > kill -s HUP 1 > > at the end of the script, as this does not necessarily succeed. > When that's the case, the package is in "half-configured" state. > > Then, when the package management system next tries to configure > it, it's *another* error that pops up: The existing SV entry. > [As far as I can tell, the "idempotency" rule of install scripts > is there to prevent such situations.] That's why the previous > report is a bit misleading. Yes, if the postinst script fails at the end, it should clean up and remove the entry in /etc/inittab again. > So, could you remove the problematic call from the install script, > or at least, make it so that a failure of that call will not imply > that the installation wasn't successful? [You could just print a > warning.] I have a problem with that. Other packages rely on the runit package to be completely configured after installation, that means the runsvdir process, the root of service supervision, must run. This is ensured, with sysvinit installed and running as process no 1, by adding the inittab entry _and_ telling init about this change (kill -HUP 1). If the last step is missing, service supervision is not started, and the runit package is not completely configured. The best is to fail installation in this situation, IMHO. I don't use a vserver environment, so I don't know how to integrate runit into it. What init is running in the vserver? Do you know how runit's service supervision can be automatically enabled within vserver on package installation? Until this is not implemented, I think the best still is to fail the installation. If you try to install the runit package, and after the failure remove the SV inittab entry, edit /var/lib/dpkg/info/runit.postinst and remove the 'kill -S HUP 1', and then run 'dpkg --configure runit', does the installation succeed, and if yes, is a runsvdir program running? BTW: I had a similar report last year, but wasn't able to cooperate with the submitter to find a solution: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=265458&archive=yes Thanks, Gerrit. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
