[CRIU] [PATCH 2/2] docs: Document -R|--leave-running option

Andrew Vagin avagin at parallels.com
Thu Oct 31 13:38:13 PDT 2013


On Thu, Oct 31, 2013 at 10:04:54PM +0400, Cyrill Gorcunov wrote:
> 
> Signed-off-by: Cyrill Gorcunov <gorcunov at openvz.org>
> ---
>  Documentation/criu.txt | 11 +++++++++++
>  1 file changed, 11 insertions(+)
> 

> diff --git a/Documentation/criu.txt b/Documentation/criu.txt
> index 7d8ca2b..41909de 100644
> --- a/Documentation/criu.txt
> +++ b/Documentation/criu.txt
> @@ -49,6 +49,17 @@ OPTIONS
>  *-s*, *--leave-stopped*::
>      Leave tasks in stopped state after checkpoint instead of killing them.
>  
> +*-R*, *--leave-running*::
> +    Leave tasks in running state after checkpoint instead of killing them. This
> +    option is pretty dangerous and should be used if and only if you understand
> +    what you are doing.
> +    If task is about to run after been checkpointed it can modify TCP connections,
> +    delete files and do other dangerous actions. So that *criu* itself can guarantee

I think you want to say:
can NOT guarantee

> +    that the next *restore* actiona will not fail. Most likely if a user starts

action

> +    *criu* with this option passed at least the file system snapshot must be
> +    done with help of 'post-dump' script.
> +    In other words, do not use it until really needed.
> +
>  *-f*, *--file* 'file'::
>      This option is valid for *show* command only and allows to see content of
>      the 'file' specified.



More information about the CRIU mailing list