On Tue, Oct 01, 2002 at 09:43:56AM +0200, Russell Coker wrote:
This is a good reason for not using debconf.
The interface between a program and libraries it uses should be defined, and
it should be designed in a way to minimise harm to other programs.
* #50595: debconf: Use of
On Tue, Oct 01, 2002 at 09:43:56AM +0200, Russell Coker wrote:
This is a good reason for not using debconf.
The interface between a program and libraries it uses should be defined, and
it should be designed in a way to minimise harm to other programs.
* #50595: debconf: Use of
I have a perl postinst script that gets stuck when running certain
external commands. For example, the line
`/etc/init.d/apache restart /dev/null 21 31 41 51`;
will freeze the postinst script so that it must be killed. The problem
has something to do with using the debconf module,
use
Hi,
Brian Nelson:
I have a perl postinst script that gets stuck when running certain
external commands. For example, the line
`/etc/init.d/apache restart /dev/null 21 31 41 51`;
will freeze the postinst script so that it must be killed. The problem
has something to do with using the
On Tue, 1 Oct 2002 09:25, Matthias Urlichs wrote:
I have a perl postinst script that gets stuck when running certain
external commands. For example, the line
`/etc/init.d/apache restart /dev/null 21 31 41 51`;
will freeze the postinst script so that it must be killed. The problem
On Tue, 1 Oct 2002 13:11, Matthias Urlichs wrote:
Russell Coker:
More specifically, it has something to do with using backticks to start
an external command, and open file descriptors. You don't KNOW which
descriptor DebConf uses.
This is a good reason for not using debconf.
IMHO
Hi,
Russell Coker:
Are you sure that it's possible to fix it in such a fashion? This might work
for Perl (I have never used the Perl interface so I don't know how it works),
Perl could do it, no problem.
but would not work for calling Debconf from Bash.
You're right -- bash lacks this
On Tue, 1 Oct 2002 14:27, Matthias Urlichs wrote:
but would not work for calling Debconf from Bash.
You're right -- bash lacks this feature. However, the context of the
original question specifically mentioned Perl (or so I remember -- anyway,
it used backticks, and nobody would use
Matthias Urlichs wrote:
IMHO it's a good reason for not mixing configuration with execution,
and it's an even better reason for fixing a bug in DebConf. Specifically,
setting the Close-On-Exec flag on the file descriptor(s) which represent
the DebConf protocol will prevent all these problems
Hi,
Joey Hess:
Matthias Urlichs wrote:
IMHO it's a good reason for not mixing configuration with execution,
and it's an even better reason for fixing a bug in DebConf. Specifically,
setting the Close-On-Exec flag on the file descriptor(s) which represent
the DebConf protocol will
I have a perl postinst script that gets stuck when running certain
external commands. For example, the line
`/etc/init.d/apache restart /dev/null 21 31 41 51`;
will freeze the postinst script so that it must be killed. The problem
has something to do with using the debconf module,
use
Hi,
Brian Nelson:
I have a perl postinst script that gets stuck when running certain
external commands. For example, the line
`/etc/init.d/apache restart /dev/null 21 31 41 51`;
will freeze the postinst script so that it must be killed. The problem
has something to do with using the
On Tue, 1 Oct 2002 09:25, Matthias Urlichs wrote:
I have a perl postinst script that gets stuck when running certain
external commands. For example, the line
`/etc/init.d/apache restart /dev/null 21 31 41 51`;
will freeze the postinst script so that it must be killed. The problem
Hi,
Russell Coker:
More specifically, it has something to do with using backticks to start an
external command, and open file descriptors. You don't KNOW which
descriptor DebConf uses.
This is a good reason for not using debconf.
IMHO it's a good reason for not mixing configuration
On Tue, 1 Oct 2002 13:11, Matthias Urlichs wrote:
Russell Coker:
More specifically, it has something to do with using backticks to start
an external command, and open file descriptors. You don't KNOW which
descriptor DebConf uses.
This is a good reason for not using debconf.
IMHO
Hi,
Russell Coker:
Are you sure that it's possible to fix it in such a fashion? This might work
for Perl (I have never used the Perl interface so I don't know how it works),
Perl could do it, no problem.
but would not work for calling Debconf from Bash.
You're right -- bash lacks this
On Tue, 1 Oct 2002 14:27, Matthias Urlichs wrote:
but would not work for calling Debconf from Bash.
You're right -- bash lacks this feature. However, the context of the
original question specifically mentioned Perl (or so I remember -- anyway,
it used backticks, and nobody would use
Matthias Urlichs wrote:
IMHO it's a good reason for not mixing configuration with execution,
and it's an even better reason for fixing a bug in DebConf. Specifically,
setting the Close-On-Exec flag on the file descriptor(s) which represent
the DebConf protocol will prevent all these problems
Hi,
Joey Hess:
Matthias Urlichs wrote:
IMHO it's a good reason for not mixing configuration with execution,
and it's an even better reason for fixing a bug in DebConf. Specifically,
setting the Close-On-Exec flag on the file descriptor(s) which represent
the DebConf protocol will prevent
19 matches
Mail list logo
