[systemd-devel] [PATCH 1/4] Adding halt binary to shutdown the system

[Gustavo Sverzut Barbieri]

On Fri, Oct 1, 2010 at 11:50 AM, 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?

rpcbind/portmapper are required to operate on nfs, no? if they go down
shouldn't you umount them? I'm not doing NFS since 2001 so I don't
remember how it work from bring-up and shutdown PoV.

-- 
Gustavo Sverzut Barbieri
http://profusion.mobi embedded systems
--------------------------------------
MSN: barbieri at gmail.com
Skype: gsbarbieri
Mobile: +55 (19) 9225-2202