From mboxrd@z Thu Jan 1 00:00:00 1970 From: Daniel Lezcano Subject: Re: Isolated shutdown? Date: Tue, 25 Aug 2009 11:58:00 +0200 Message-ID: <4A93B5A8.7080104@free.fr> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: containers-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org Errors-To: containers-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org To: Scott Helvick Cc: containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org List-Id: containers.vger.kernel.org Scott Helvick wrote: > Hello all, > > I've set up a system container with a mostly-complete filesystem, built from > scratch. However, I'm having several minor issues, which leads me to > believe I'm misunderstanding something about how lxc works. For one thing, > I find myself unable to kill processes within the container itself (process > handling is a whole other issue)... yet when I run 'shutdown', it not only > shuts down the container, but also the host! Somehow I don't think this was > a design decision. :-) > > Any tips would be appreciated. > It is not yet supported. You can drop PR_CAPBSET_DROP capability for your system container, that will avoid to poweroff your host. I proposed to send a signal to the parent of the process 1, telling if the container was doing poweroff or reboot but I didn't have any response :(