All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sukadev Bhattiprolu <sukadev-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
To: Oren Laadan <orenl-eQaUEPhvms7ENvBUuze7eA@public.gmane.org>
Cc: Containers
	<containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org>
Subject: Re: --freezer option to /bin/restart
Date: Mon, 29 Mar 2010 12:56:37 -0700	[thread overview]
Message-ID: <20100329195637.GA26618@us.ibm.com> (raw)
In-Reply-To: <4BAFD132.7040704-eQaUEPhvms7ENvBUuze7eA@public.gmane.org>

>>>> Is there a way to specify that the restarted application belong
>>>> to a new (yet-to-be created) cgroup AND to leave the application
>>>> FROZEN after restart ? Or would we need a new command line option
>>>> and field in 'struct app_restart_args' to specify this ?
>>> This is exactly what --freezer does. Well, alsmot - except for
>>> "yet-to-be created". Do you want 'restart' to create the cgroup
>>> if it doesn't exist ?

If we restart with one of the CLONE_NEW flags like CLONE_NEWPID, a
new cgroup is automatically created right ? So, in effect, all I want
at this point is to be able to leave the restarted application in the
FROZEN state (ie specify the RESTART_FROZEN flag to sys_restart()).

>>
>> I thought that was what Suka was asking for.
>
> If he wants to add it to the 'restart' utility, then sure, with
> a proper argument.

Ok. Will add a new field to struct app_restart_args to pass the
RESTART_FROZEN flag to sys_restart(). We can then either add -F option
or allow --freezer without argument to choose this behavior.

  parent reply	other threads:[~2010-03-29 19:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-27 19:14 --freezer option to /bin/restart Sukadev Bhattiprolu
     [not found] ` <20100327191453.GA1533-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2010-03-28 15:16   ` Oren Laadan
     [not found]     ` <4BAF72C6.1020806-eQaUEPhvms7ENvBUuze7eA@public.gmane.org>
2010-03-28 21:32       ` Serge E. Hallyn
     [not found]         ` <20100328213254.GA12661-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2010-03-28 21:59           ` Oren Laadan
     [not found]             ` <4BAFD132.7040704-eQaUEPhvms7ENvBUuze7eA@public.gmane.org>
2010-03-28 22:33               ` Serge E. Hallyn
2010-03-29 19:56               ` Sukadev Bhattiprolu [this message]
     [not found]                 ` <20100329195637.GA26618-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2010-03-29 20:20                   ` Serge E. Hallyn

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100329195637.GA26618@us.ibm.com \
    --to=sukadev-23vcf4htsmix0ybbhkvfkdbpr1lh4cv8@public.gmane.org \
    --cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
    --cc=orenl-eQaUEPhvms7ENvBUuze7eA@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.