Changes

Jump to navigation Jump to search
12 bytes removed ,  16:55, 30 April 2013
crtools -> criu
Line 43: Line 43:  
== Checkpoint and restore TCP connection ==
 
== Checkpoint and restore TCP connection ==
   −
With the above sockoptions dumping and restoring TCP connection becomes possible. The crtools just reads the socket
+
With the above sockoptions dumping and restoring TCP connection becomes possible. The criu just reads the socket
 
state and restores it back letting the protocol resurrect the data sequence.
 
state and restores it back letting the protocol resurrect the data sequence.
   Line 49: Line 49:  
no packets from peer should enter the stack, otherwise the RST will be sent by a kernel. In order to do so a simple
 
no packets from peer should enter the stack, otherwise the RST will be sent by a kernel. In order to do so a simple
 
netfilter rule is configured that drops all the packets from peer to a socket we're dealing with. This rule sits
 
netfilter rule is configured that drops all the packets from peer to a socket we're dealing with. This rule sits
in the host netfilter tables after the crtools dump command finishes and it should be there when you issue the
+
in the host netfilter tables after the criu dump command finishes and it should be there when you issue the
crtools restore one.
+
criu restore one.
   −
That said, the command line option --tcp-established should be used when calling crtools to explicitly state, that the
+
That said, the command line option --tcp-established should be used when calling criu to explicitly state, that the
 
caller is aware of this "transitional" state of the netfilter.
 
caller is aware of this "transitional" state of the netfilter.
  

Navigation menu