Action scripts - Revision history

Radostin: /* Library */ Replace 'criu_set_notify' with 'criu_set_notify_cb'

2020-02-28T22:48:41Z

Library: Replace 'criu_set_notify' with 'criu_set_notify_cb'

Radostin: Add note for orphan-pts-master

2019-02-16T19:57:09Z

Add note for orphan-pts-master

Radostin: Update list of supported hooks

2019-02-12T19:09:47Z

Update list of supported hooks

Kir: link to docker; don't link twice

2015-04-08T16:33:39Z

link to docker; don't link twice

Kir: minor formatting and English fixes

2015-04-08T16:31:25Z

minor formatting and English fixes

Saied Kazemi: /* RPC */

2015-04-08T16:16:48Z

RPC

Saied Kazemi at 17:14, 2 January 2015

2015-01-02T17:14:18Z

Xemul: Categorized

2014-12-31T10:39:08Z

Categorized

Xemul at 10:31, 31 December 2014

2014-12-31T10:31:12Z

Saied Kazemi at 18:33, 30 December 2014

2014-12-30T18:33:33Z

@@ Line 44: / Line 44: @@
 == Library ==
-When using a library, one can set up a callback using the <code>criu_set_notify</code> routine.
+When using a library, one can set up a callback using the <code>criu_set_notify_cb</code> routine.
 [[Category:HOWTO]]
 [[Category:API]]

@@ Line 32: / Line 32: @@
 ;<code>orphan-pts-master</code>
-: called after master pty is opened and unlocked (used by Docker)
+: called after master pty is opened and unlocked (used by Docker). Used only in RPC mode, and the notification message contains a file descriptor for the master pty.
 == CLI ==

@@ Line 1: / Line 1: @@
 With the <code>--action-script</code> command line option, CRIU can call your action scripts (also known as hooks) at various stages of dumping/restoring. The following hooks are available:
 ;<code>network-lock</code>
@@ Line 7: / Line 19: @@
 : requested to unlock a container network (used by Docker and LXC)
-;<code>post-dump</code>
+;<code>setup-namespaces</code>
-: called when CRIU finished dumping tasks before unfreezing them
+: called when the root task is alive and new set of namespaces is created to set them up
-;<code>post-restore</code>
+;<code>post-resume</code>
-: called when CRIU has finished restoring tasks before unlocking the network
+: called at the very end, when everything is restored and processes were resumed
-;<code>setup-namespaces</code>
+;<code>orphan-pts-master</code>
-: called when the root task is alive and new set of namespaces is created to set them up
+: called after master pty is opened and unlocked (used by Docker)
 == CLI ==

@@ Line 2: / Line 2: @@
 ;<code>network-lock</code>
-: request to lock a container network (used by Docker and [[LXC]])
+: request to lock a container network (used by [[Docker]] and [[LXC]])
 ;<code>network-unlock</code>
-: requested to unlock a container network (used by Docker and [[LXC]])
+: requested to unlock a container network (used by Docker and LXC)
 ;<code>post-dump</code>

@@ Line 1: / Line 1: @@
-With the --action-script command line option, CRIU can call your action scripts (also known as hooks) at various stages of dumping/restoring. Hooks can be one of
+With the <code>--action-script</code> command line option, CRIU can call your action scripts (also known as hooks) at various stages of dumping/restoring. The following hooks are available:
-;network-lock
+;<code>network-lock</code>
 : request to lock a container network (used by Docker and [[LXC]])
-;network-unlock
+;<code>network-unlock</code>
 : requested to unlock a container network (used by Docker and [[LXC]])
-;post-dump
+;<code>post-dump</code>
 : called when CRIU finished dumping tasks before unfreezing them
-;post-restore
+;<code>post-restore</code>
 : called when CRIU has finished restoring tasks before unlocking the network
-;setup-namespaces
+;<code>setup-namespaces</code>
 : called when the root task is alive and new set of namespaces is created to set them up
-== CLI ==
+These hooks are added with the <code>--action-script ''shell-code-to-execute''</code> option. When called, the <code>CRTOOLS_SCRIPT_ACTION</code> environment is set to a value determining which type of action is performed.
 == RPC ==
-In case of RPC, action scripts are implemented as notifications -- once CRIU service wants to execute a script it sends an RPC message to caller and waits for it to respond with <code>criu_req</code> message having <code>notify_success = true</code>.
+In case of RPC, action scripts are implemented as notifications. Once CRIU service wants to execute a script, it sends an RPC message to the caller and waits for it to respond with <code>criu_req</code> message having <code>notify_success = true</code>.
 == Library ==
-When using a library one can setup a callback using the <code>criu_set_notify</code> routine.
+When using a library, one can set up a callback using the <code>criu_set_notify</code> routine.
 [[Category:HOWTO]]
 [[Category:API]]

← Older revision		Revision as of 17:14, 2 January 2015
Line 28:		Line 28:
	When using a library one can setup a callback using the <code>criu_set_notify</code> routine.		When using a library one can setup a callback using the <code>criu_set_notify</code> routine.

		+	[[Category:HOWTO]]
	[[Category:API]]		[[Category:API]]

← Older revision		Revision as of 10:39, 31 December 2014
Line 27:		Line 27:

	When using a library one can setup a callback using the <code>criu_set_notify</code> routine.		When using a library one can setup a callback using the <code>criu_set_notify</code> routine.
		+
		+	[[Category:API]]