mir/criu
2
0
Fork 0
mirror of https://github.com/checkpoint-restore/criu synced 2025-08-31 06:15:24 +00:00
Code Issues Releases Wiki Activity

criu(8): Move --tcp-close under restore

Browse Source 
The --tcp-close option was introduced with commit

2c37042821
tcp: Add tcp-close option to restore connected TCP sockets in closed state

This options is applicable only for restore. Therefore, move the
documentation from 'dump' to 'restore'.

Signed-off-by: Radostin Stoyanov <rstoyanov1@gmail.com>
Signed-off-by: Andrei Vagin <avagin@gmail.com>
This commit is contained in:
Radostin Stoyanov
2019-01-17 08:43:33 +00:00
committed by Andrei Vagin
parent e4fa84a32a
commit b42b3e2ada
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
Documentation/criu.txt
View File

@@ -268,9 +268,6 @@ For example, the command line for the above example should look like this:
The TCP stack on the client side is expected to handle the
re-connect gracefully.
*--tcp-close*::
Restore connected TCP sockets in closed state.
*--evasive-devices*::
Use any path to a device file if the original one is inaccessible.
@@ -439,6 +436,9 @@ The 'mode' may be one of the following:
the network has been locked between *dump* and *restore* phases so other
side of a connection simply notice a kind of lag.
*--tcp-close*::
Restore connected TCP sockets in closed state.
*--veth-pair* 'IN'*=*'OUT'::
Correspondence between outside and inside names of veth devices.