Package: memlockd Version: 0.03 Severity: serious I just installed memlockd and saw the following output:
Selecting previously deselected package memlockd.
(Reading database ... 113626 files and directories currently installed.)
Unpacking memlockd (from .../memlockd_0.03_amd64.deb) ...
Setting up memlockd (0.03) ...
Starting memlockd: memlockd.
Starting memlockd: memlockd.
It looks like two daemons were indeed started:
13885 ? SLs 0:00 /usr/sbin/memlockd -u memlockd
13907 ? SLs 0:00 /usr/sbin/memlockd -u memlockd
/var/run/memlockd.pid contains only "13885". /etc/init.d/memlockd only
kills the first one; the second one has to be killed by hand.
In the configure stage of the postinst, "/etc/init.d/memlockd restart"
is called directly (this is a policy violation, see #438885), and then
later dh_installinit adds code to the end of the script which can call
the init script again.
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.22-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages memlockd depends on:
ii libc6 2.6.1-1 GNU C Library: Shared libraries
ii libstdc++6 4.2.1-4 The GNU Standard C++ Library v3
memlockd recommends no packages.
-- no debconf information
--
Robert Edmonds
[EMAIL PROTECTED]
signature.asc
Description: Digital signature
