Bug#1033311: sysvinit-utils: pidof not always returning a pid when using the full path to a program

Mark Hindley mark at hindley.org.uk
Wed Mar 22 11:31:04 GMT 2023


Thanks for this.

On Wed, Mar 22, 2023 at 08:40:20AM +0100, Markus Fischer wrote:
> Package: sysvinit-utils
> Version: 3.06-2
> Severity: normal
> X-Debbugs-Cc: none
> Dear Maintainer,
> Passing the full path of a binary to the pidof command does not always
> return a pid although the process is running and the man page of the
> pidof command explicitly notes that it can be used that way.
> This might be related to the fact that all programs with which I tested
> this and which show this unexpected behaviour were symlinks (i.e.,
> "which <PROGRAM>" returned a symlink).

Yes, I just tried with vim.basic which is not a symlink on my system and both

 pidof vim.basic
 pidof $(which vim.basic)

work as expected.

> However, on Debian Bullseye the
> behaviour is as I expected it.

So this appears to be a change in behaviour. I suspect this is an inadvertent
side-effect of 0b695c7e0b1cac60ed77c56f224e296f023b652e.

Jesse, or was it intentional?



More information about the Debian-init-diversity mailing list