Difference between revisions of "CLI/opt/--skip-in-flight"
Jump to navigation
Jump to search
(Redirected page to TCP repair TODO) |
(Describe --skip-in-flight option) Tag: Removed redirect |
||
| Line 1: | Line 1: | ||
| − | + | ''Main article: [[TCP connection]]'' | |
| + | |||
| + | In-flight connections can happen on sockets which do not yet have a full [https://en.wikipedia.org/wiki/Transmission_Control_Protocol#CONNECTION-ESTABLISHMENT established connection]. | ||
| + | For instance, when establishing a TCP connection using a three-way [https://en.wikipedia.org/wiki/Handshaking handshake], '''SYN''' and '''SYN-ACK''' have been exchanged but the final '''ACK''' is not send back to the server. | ||
| + | |||
| + | CRIU can handle the checkpoint of sockets in this state with the <code>--skip-in-flight</code> option, which will ignore not yet completely established TCP connections. On restore the client is expected to handle the re-connection. | ||
| + | |||
[[Category:CLI]] | [[Category:CLI]] | ||
| + | [[Category:Sockets]] | ||
Latest revision as of 20:19, 2 January 2019
Main article: TCP connection
In-flight connections can happen on sockets which do not yet have a full established connection. For instance, when establishing a TCP connection using a three-way handshake, SYN and SYN-ACK have been exchanged but the final ACK is not send back to the server.
CRIU can handle the checkpoint of sockets in this state with the --skip-in-flight option, which will ignore not yet completely established TCP connections. On restore the client is expected to handle the re-connection.