Package: sysvinit
Version: 2.88dsf-34
Followup-For: Bug #687410
This is not only a problem from non-privileged users.
When using lxc and when containers are running, pidof /sbin/init returns all
containers init processes, and that makes the kill command fail, and thus
upgrades fail. I was hit by
On Wed, Sep 12, 2012 at 04:21:02PM +0200, Michael Stapelberg wrote:
> Hi,
>
> Daniel Kahn Gillmor writes:
> > PID="$(pidof /sbin/init || true)"
> > [...]
> > kill -s USR1 "$PID"
> The comment in the file states:
>
> # PID of init; may not always be 1. Use for se
Hi,
Daniel Kahn Gillmor writes:
> PID="$(pidof /sbin/init || true)"
> [...]
> kill -s USR1 "$PID"
The comment in the file states:
# PID of init; may not always be 1. Use for sending signals
# and checking if init is running.
PID="$(pidof /sbin/in
Package: sysvinit
Version: 2.88dsf-31
Severity: normal
sysvinit.postinst has the following code:
PID="$(pidof /sbin/init || true)"
[...]
kill -s USR1 "$PID"
But a normal user can cause "pidof /sbin/init" to produce more than
one output, e.g. with "chpst -b /sbin/init ca
4 matches
Mail list logo
