[Pkg-sysvinit-devel] Bug#476698: Bug#476698: killall5 should not kill fuse filesystems

[Goswin von Brederlow]

Petter Reinholdtsen <pere at hungry.com> writes:

> [Goswin von Brederlow]
>> For one thing because there is no such thing as an "omitpid feature"
>> in killall5. Only pidof has it.
>
> Hm.
>
> I just tested it, and it worked for me.  How are you testing it?  I
> changed init.d/klogd stop location to be after sendsigs and made sure
> klogd made a symlink to the pidfile from
> /lib/init/rw/sendsigs.omit.d/klogd, and this got rid of the error
> message from the klogd stop script which normally show up in this
> setting when sendsigs already killed the klogd process.

I've read (and pasted) the source.

With an omitpid file the killa5 will just give an error and not kill
anything. So obviously your klogd will still be running then. But so
will everything else.

>> The other is that fuse filesystems can fork and thereby add new
>> pids. Depending on the threading modell in use even threading will
>> create pids. And you can't add the pids of children to the omitpid
>> file without race conditions.
>
> Well, if the fuse file systems do not want to accept the limits of the
> omitpid feature, they can either accept to be killed, or we will have
> to come up with a better way to do it.

For our unionfs fuse that is probably workable. Don't know about
httpfs but I would hope it doesn't fork wgets to fetch files.

MfG
        Goswin