== Limitations ==
Named unix sockets with stream/seqpacket options can't be dumped\restored now, see plan below.
== What to do with stream/seqpacket? ==
Such sockets cannot be just dumped and restored as once we dump one end, the other one seen EOF on socket and may close one. The plan for this is to extend the --ext-unix-sk semantics to work like this
* On dump the <code>--ext-unix -sk $id</ code> says that socket with $id is OK to be disconnected * On restore the <code>--ext-unix-sk$id[=$path]</code> says that the socket $id should be reconnected back to the path it say on dump (or to the $path).
== What to do with socketpair()-s? == Unnamed unix sockets created with socketpair() systemcall can be dumped and restored. For dump socketpair put inode of this socket in <code>--ext-unix-sk</code> option, for example:
criu dump - D images - o dump.log - v4 --ext-unix-sk= 11890815 -t 16528</code>
For restore socketpair the server should create new pair and call criu restore asking it to [[Inheriting FDs on restore|inherit]] one. Example of command:
criu restore -d -D images -o restore.log --pidfile restore.pid -v4 -x --inherit-fd fd:socket:</code>
test source code also available for this feature and can be found in criu source tree under test/socketpairs.
== See also ==