[458] in athena10
Re: Login chroots and interaction with updates
daemon@ATHENA.MIT.EDU (Kenneth Arnold)
Wed Aug 20 12:55:55 2008
Message-ID: <48AC4C63.5070001@mit.edu>
Date: Wed, 20 Aug 2008 12:54:59 -0400
From: Kenneth Arnold <kcarnold@MIT.EDU>
MIME-Version: 1.0
To: ghudson@mit.edu
CC: athena10@mit.edu
In-Reply-To: <200808201649.m7KGn6oH020764@outgoing.mit.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
ghudson@MIT.EDU wrote:
>> * Force-unmount the login snapshot and destroy it.
>>
>
> So to unmount the login snapshot we first have to kill any processes
> which reference it. Killing all processes belonging to the user is a
> start, but (1) it's possible for processes to be unkillable in disk
> wait, and (2) the user could have started processes as root. Both
> cases should be uncommon but we have to handle them.
>
> I guess the best approach is to kill off all processes owned by the
> user, attempt the unmount, and then reboot if that fails. The login
> snapshot can then be destroyed by the PreSession hook after the
> reboot.
>
I think `fuser -km /the/chroot/mountpoint` should work for user and root
processes.
-Ken
