[PATCHv2,3/6] criu(8): Move --tcp-close under restore

Submitted by Radostin Stoyanov on Jan. 13, 2019, 3:25 p.m.

Details

Message ID 20190113152542.20315-3-rstoyanov1@gmail.com
State New
Series "Series without cover letter"
Headers show

Commit Message

Radostin Stoyanov Jan. 13, 2019, 3:25 p.m.
The --tcp-close option was introduced with commit

2c37042821906f013634e305899cb25ff1a5a7b1
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>
---
 Documentation/criu.txt | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

Patch hide | download patch | download mbox

diff --git a/Documentation/criu.txt b/Documentation/criu.txt
index 80ce1124a..0a024292d 100644
--- a/Documentation/criu.txt
+++ b/Documentation/criu.txt
@@ -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.