On Tue, 22.04.14 07:48, Nikolaus Rath (nikol...@rath.org) wrote: > Lennart Poettering <lenn...@poettering.net> writes: > > On Mon, 21.04.14 19:05, Diogo Vieira (d...@eurotux.com) wrote: > > > >> Hello, > >> > >> I'm trying to create a unit to automatically mount a fuse filesystem > >> known as S3QL, which is the one in question in this older thread: > >> http://lists.freedesktop.org/archives/systemd-devel/2012-May/005062.html. > >> The > >> problem seems to be that after unmounting the filesystem it still > >> needs network access to transfer data. Can someone tell me if it's > >> already possible to create a mount unit configuration that covers this > >> or should I go with a service unit? And if I need a service unit how > >> do I deal with the chance of someone manually unmounting the > >> filesystem thus making (I believe, didn't test it) the service status > >> return successfully when in fact the filesystem's not mounted? I don't > >> know if it's useful, but I'm trying this on Fedora. > > > > systemd will invoke /bin/mount when mounting a file system, and > > /bin/umount when unmountin it. fuse file systems may fork off background > > processes from there, that will be kept around while the file system is > > mounted, and terminated atfer the file system is unmounted again. > > Is there any way to avoid that, and give the background process some > time to terminate on its own?
It has that. We always send SIGTERM first, and after a timeout of 90s (by default) this is followed by SIGKILL if the process didn't exit on its own by then. Your fuse file system should simply handle SIGTERM properly, like any other UNIX process... Lennart -- Lennart Poettering, Red Hat _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
