Difference between revisions of "Action scripts"
Jump to navigation
Jump to search
| Line 12: | Line 12: | ||
;setup-namespaces | ;setup-namespaces | ||
: called when the root task is alive and new set of namespaces is created to set them up | : called when the root task is alive and new set of namespaces is created to set them up | ||
| + | |||
| + | == RPC == | ||
| + | |||
| + | In case or RPC, action scripts are implemented as notifications -- once CRIU service wants to execute a script it send an RPC message to caller and waits for it to respond with <code>criu_req</code> message having <code>notify_success = true</code>. | ||
Revision as of 12:46, 25 June 2014
The criu can call your hooks on various stages of dumping/restoring. These hooks are added with the --action-script shell-code-to-execute option. When called, the CRTOOLS_SCRIPT_ACTION environment is set to a value determining which type of action is performed. It can be one of
- network-lock
- request to lock an LXC container network
- network-unlock
- requested to unlock an LXC container network
- post-dump
- called when CRIU finished dumping tasks before unfreezing them
- setup-namespaces
- called when the root task is alive and new set of namespaces is created to set them up
RPC
In case or RPC, action scripts are implemented as notifications -- once CRIU service wants to execute a script it send an RPC message to caller and waits for it to respond with criu_req message having notify_success = true.