[Pkg-sysvinit-devel] Bug#476698: Bug#476698: killall5 should not kill fuse filesystems
Petter Reinholdtsen
pere at hungry.com
Tue May 20 06:35:26 UTC 2008
[Goswin von Brederlow]
> we use fuse-unionfs for /etc and /usr on a pool of systems. When
> rebooting killall5 will kill all processes execpt init and itself
> causing the fuse filesystems to be killed without umount. In our
> case the next access to /etc or /usr will block because there will
> be no process left to service the request.
Why does it not work to use the omitpid feature of sendsigs? It was
written for cases like this.
> The attached patch adds a test for fuse filesystem and leaves them
> alone. This allows any of the many fuse filesystems to be used for
> system directories.
It seem like a bad idea to add file system specific code in killall5,
and I would prefer this to be done using the omitpid feature instead.
> It also changes the cwd to /proc and changes readproc() to use
> relative paths. This avoids access() calls to / that would deadlock
> if / is a fuse filesystem.
This sound like a good idea. Can you make a clean patch to use
relative paths?
Btw, the stat() patch in #476695 will be included in the next upload.
Happy hacking,
--
Petter Reinholdtsen
More information about the Pkg-sysvinit-devel
mailing list