Re: Going nuts over debconf

On Thu, 03 Nov 2005, Steve Langasek wrote: On Thu, Nov 03, 2005 at 10:32:07PM -0500, Peter S Galbraith wrote: Problem summary: Using debconf and rc.d script hangs package installation I am merging packages `powstatd' and `powstad-crypt' into a single new `powstatd' package with encryption

Re: Going nuts over debconf

Henrique de Moraes Holschuh wrote: And the proper fix is to call db_stop AND of course fix the daemon to close open fds it doesn't need. Unfortunately, there are only kludgy ways to do so as the kernel won't tell you which FDs you have that are open. That's not quite true. On Linux you can

Re: Going nuts over debconf

On Sat, 05 Nov 2005, Cameron Patrick wrote: Henrique de Moraes Holschuh wrote: And the proper fix is to call db_stop AND of course fix the daemon to close open fds it doesn't need. Unfortunately, there are only kludgy ways to do so as the kernel won't tell you which FDs you have that are

Going nuts over debconf

Hi, Problem summary: Using debconf and rc.d script hangs package installation -- I am merging packages `powstatd' and `powstad-crypt' into a single new `powstatd' package with encryption enabled. I wrote a debconf script that displays a warning in certain cases when the configuration file must

Re: Going nuts over debconf

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, Nov 03, 2005 at 10:32:07PM -0500, Peter S Galbraith wrote: Problem summary: Using debconf and rc.d script hangs package installation I am merging packages `powstatd' and `powstad-crypt' into a single new `powstatd' package with encryption

Re: Going nuts over debconf

Steve Langasek [EMAIL PROTECTED] wrote: Problem summary: Using debconf and rc.d script hangs package installation I am merging packages `powstatd' and `powstad-crypt' into a single new `powstatd' package with encryption enabled. I wrote a debconf script that displays a warning in