[Pkg-clamav-devel] Bug#760219: Bug#760219: clamav-daemon: use of --name in init.d's stop-start-daemon causes failure to stop in certain virtualized environments

[Sebastian Andrzej Siewior]

On 2014-08-31 22:04:33 [-0400], Daniel Dickinson wrote:
> /etc/init.d/clamav-deamon uses --name in it's start-stop-daemon calls for stop and restart.
> 
> This fails when process names are not available due to use of certain virtualized environments
> use as kfreebsd in freebsd jail (others have the same issue from reports I've read however this
> is what I am use) due to limited /proc.

This sound like an interresting limitation. Just to make it clear: a ps
shows pid but not the process name that belongs to it? If so how do you
make know what is running on the machine then?

Don't you have the same problem with other daemons like unbound or
dovecot?

> 
> Changin relying solely on PIDFILE fixes the issue (i.e. drop --name $DAEMON)

We had a bug reported that it is unsecure not checking the name of the
process and only using the PIDFILE. The reason was that the daemon migh
segfault (or gets killed by other means) and another unrelated process
gets the same PID assigned that was used by that daemon. And so a stop
would kill another process. That is why --name was added.
Do you have any other suggestions to get this wokring for you?

Sebastian