[Pkg-clamav-devel] Bug#760219: Bug#760219: Acknowledgement (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-09-06 09:35:09 [-0400], Daniel Dickinson wrote:
> This can be downgraded to lowest, maybe even wishlist priorty as, at
> least in the scenario I'm in, which is the only one I have sufficient
> information to base an assessment on, the jail wasn't using linprocfs
> (freebsd linux compability profs) but instead the freebsd native procfs.
>  Given that linprocfs exists and things work properly when using it,
> there is no great urgency, on kfreebsd, to mess with a whack of
> initscripts and/or system tools (like start-stop-daemon).

Not sure if this is an answer to my questions from earlier or not.
But let me summerize this a little and please shout if I got something
wrong here:
- this problem is specific to kfreebsd port using jails
- and then only if freebsd native procfs is used instead of linprocfs.

So. Based on this, why would one not want to use linprocfs in the first
place?
If there is no reason to do so then I would close this bug (and his two
brothers).
Is there a way to detect if linprocfs has been used? Because it would
make sense to teach start-stop-daemon to check for this.

> Regards,
> 
> Daniel

Sebastian