Re: [systemd-devel] Unit configuration for S3QL filesystem
On Wed, 23.04.14 20:39, Nikolaus Rath (nikol...@rath.org) wrote: Lennart Poettering lenn...@poettering.net writes: 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. Apologies, I couldn't deduce that from your above statement, nor was I able to find this in systemd.mount(5). The latter only talks about processes being killed when the mount command did not return after TimeoutSec seconds. Does this mean (hypothetically, I know it wouldn't be helpful) that I could also use the other options from systemd.kill(5), so that if e.g. I set KillMode=process any child processes of the mount helper will actually be left alive? Yes, the system.mount(5) man page is actually pretty clear that the options from system.kill(5) apply too. It references that man page at least four times... Lennart -- Lennart Poettering, Red Hat ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Unit configuration for S3QL filesystem
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? Best, -Nikolaus -- GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F »Time flies like an arrow, fruit flies like a Banana.« ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Unit configuration for S3QL filesystem
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
Re: [systemd-devel] Unit configuration for S3QL filesystem
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. Lennart -- Lennart Poettering, Red Hat ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
