Dear maintainer(s) of radvd,

it appears that radvd uses `pidof` in its testsuite, or that
at least one of its binary packages uses `pidof` at runtime.
Historically, `pidof` was provided by the Essential package
`sysvinit-tools`, making an explicit dependency unnecessary. However
`pidof` will soon be moved to `procps` and will no longer be part of
the Essential set.

Please add an explicit dependency on `procps`:

* via the `Depends:` field of all binary packages of radvd
  that use `pidof` at runtime;
* via the `Build-Depends:` field of radvd, if `pidof` is
  used in tests run at build-time;
* via the `Depends:` field of `debian/control/tests`, if `pidof` is
  used in autopkgtests.

To prevent any disruption for users of radvd, please add
this dependency now, before `pidof` is moved from `sysvinit-utils` to
`procps`. Alternatively, you could remove all uses of `pidof`.

It is believed that radvd uses `pidof` due to the following
code snippets:

```
path: radvd_1:2.20-1/debian/tests/daemons
sysctl -w net.ipv6.conf.all.forwarding=1
/etc/init.d/${DAEMON} restart > /dev/null 2>&1
if pidof -x $DAEMON > /dev/null; then
    echo "OK"
else
```

Feel free to close this issue if this is a false positive (for example
if this code is in an unreachable code path).

Regards,

[...]
[...]

Usually it's not a good idea to directly invoke init scripts, but in
this test-suite it might be ok (I don't know).
However if it is ok to directly invoke the init script, then that should
also be done to check the status. i.e.

```
/etc/init.d/${DAEMON} restart > /dev/null 2>&1
if /etc/init.d/${DAEMON} status > /dev/null 2>&1 ; then
```

That should eliminate the need for pidof.

Regards,
Andreas Henriksson