Changes

== Per-task logging on restore ==

== Per-task logging on restore ==

By default criu puts all logs into one log file specified by {{Opt|--log-file}} option. If you want to split restoration logs on per-pid basis you can use the {{Opt|--log-pid}} option. The logs of a <code>''pid''</code> task will appear in a <code>''logfile''.''pid''</code> file.

By default criu puts all logs into one log file specified by {{Opt|--log-file|file}} option. If you want to split restoration logs on per-PID basis you can use the {{Opt|--log-pid}} option. The logs of a task having PID of N will appear in a <code>''file''.''N''</code> file.

== Knowing a new PID of restored task ==

== Knowing a new PID of restored task ==

When you restore a process tree that lives inside a PID namespace, the pid of a new task will be generated by the system (since the pids sitting in image files are treated as virtual, i.e. seen in namespace ones). To find this pid out you can use the {{Opt|--pidfile|file}} option to make criu put the new PID into <code>''file''</code>.

When you restore a process tree that lives inside a PID namespace, the PID of a new task will be generated by the system (since the PIDs sitting in image files are treated as virtual, i.e. as seen in a PID namespace). To find out the PID, one can use the {{Opt|--pidfile|file}} option to make CRIU put the new PID into <code>''file''</code>.

== Restoring a veth pair of devices ==

== Restoring a VETH pair of devices ==

When you restore a net namespace with a veth device end in it, criu will create the other end of the pair in the net namespace you launch criu from. By default it's name will be the one generated by veth kernel driver. Not to scan through all the net devices trying to fine one you can use the {{Opt|--veth-pair|ns-dev:host-dev}} option. When used a device named <code>''ns-dev''</code> in a newly restored namespace will be linked with the <code>''host-dev''</code> one in the criu namespace.

When you restore a net namespace with a VETH device end in it, CRIU will create the other end of the pair in the net namespace you launch CRIU from. By default its name will be the one generated by the <code>veth</code> kernel driver. Not to scan through all the net devices trying to find one, you can use the {{Opt|--veth-pair|ns-dev'':''host-dev}} option. When used a device named <code>''ns-dev''</code> in a newly restored namespace will be linked with the <code>''host-dev''</code> one in the CRIU namespace.

== Action scripts ==

== Action scripts ==