On Fri, Oct 1, 2010 at 11:50 AM, Michael Biebl <[email protected]> wrote: > 2010/10/1 Gustavo Sverzut Barbieri <[email protected]>: >> On Fri, Oct 1, 2010 at 11:36 AM, Michael Biebl <[email protected]> wrote: >>> 2010/10/1 Gustavo Sverzut Barbieri <[email protected]>: >>>> From: Fabiano Fidencio <[email protected]> >>>> >>>> This functions are working as follows: >>>> - Send a SIGTERM to all process >>>> - Send a SIGKILL to all process >>>> - Try to umount all mount points >>>> - Try to remount read-only all mount points that can't >>>> be umounted >>> >>> What about remote mounts (e.g. NFS requiring portmap) or fuse mounts? >>> If you kill their processes before unmounting you can not unmount >>> those fs cleanly. >> >> IMO these should be stopped while at systemd's units. After all, if >> units were started and then stopped by systemd, the server processes >> are over already. > > Sorry, I don't understand what you are saying. > > Say I have an NFS and/or fuse mount in /etc/fstab. > Which unit file you are talking about should be dealing with > unmounting this nfs mount?
NFS is being umounted. I'm passing MNT_FORCE to umount2 (in umount.c) About fuse, Which is the problem in try to umount using umount2? > > > -- > Why is it that all of the instruments seeking intelligent life in the > universe are pointed away from Earth? > _______________________________________________ > systemd-devel mailing list > [email protected] > http://lists.freedesktop.org/mailman/listinfo/systemd-devel > -- Fabiano Fidêncio ProFUSION embedded systems http://www.profusion.mobi _______________________________________________ systemd-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/systemd-devel
