[systemd-devel] [PATCH 1/4] Adding halt binary to shutdown the system
lennart at poettering.net
Fri Oct 1 09:43:18 PDT 2010
On Fri, 01.10.10 16:50, Michael Biebl (mbiebl at gmail.com) wrote:
> 2010/10/1 Gustavo Sverzut Barbieri <barbieri at profusion.mobi>:
> > On Fri, Oct 1, 2010 at 11:36 AM, Michael Biebl <mbiebl at gmail.com> wrote:
> >> 2010/10/1 Gustavo Sverzut Barbieri <barbieri at profusion.mobi>:
> >>> From: Fabiano Fidencio <fidencio at profusion.mobi>
> >>> 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?
All mount units have an implicit conflicts dependency on
umount.target. Activating the latter means that all mount points go
away. This is done as part of shutdown.
Lennart Poettering - Red Hat, Inc.
More information about the systemd-devel