of the postinst script could be made more robust to handle the
case where the config file is missing:
# Copy the passwd/group files to the TMP directory
# to avoid warnings when rkhunter is first run.
# This is normally done by the installer script.
rkhtmpdir=$(grep '^TMPDIR' /etc/rkhunter.conf
Nevermind my last email, I got the wrong bug number :(
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20141128114157.go29...@akranes.dyndns.org
Hi
I have a command line in postinst script of a package that works ok
outside a package install context .
one line is causing an error :
cat /proc/file | grep XYfile
without the grep - no error
with the grep the postinstall terminates with error(below) .
dpkg: error processing
On Tue, Sep 7, 2010 at 9:04 PM, Zvi Dubitzky d...@il.ibm.com wrote:
Hi
I have a command line in postinst script of a package that works ok
outside a package install context .
one line is causing an error :
cat /proc/file | grep XY file
without the grep - no error
with the grep
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 7 Sep 2010 23:04:56 +0300
Zvi Dubitzky d...@il.ibm.com wrote:
Hi
I have a command line in postinst script of a package that works ok
outside a package install context .
one line is causing an error :
cat /proc/file | grep XY
11:09 \_ kpsewhich --var-value=TEXMFMAIN
So it seems two postinst script were running at the same time (note that
tetex-bin depends on tetex-base). Furthermore, the second one seems to
have no parent except init, while the other one has dpkg --configure
tetex-base tetex-bin
Dear Frank,
On Mon, 06 Nov 2006, Frank Küster wrote:
So it seems two postinst script were running at the same time (note that
tetex-bin depends on tetex-base). Furthermore, the second one seems to
have no parent except init, while the other one has dpkg --configure
tetex-base tetex-bin
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
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
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
Are there any examples of creating a mysql database in a postinst script
anywhere? I'm having troubles with entering the password for:
mysqladmin create dbname -p
Any ideas for how I should handle this?
I'm attempting to package an account administration system that I
developed for K-12
27 matches
Mail list logo
