2,257
edits
Changes
→Usage
== Usage ==
== Usage ==
<pre>
<pre>
usage: crit [-h] [-i IN] [-o OUT] [--pretty] {decode,encode}
usage: crit [-h] {decode,encode,info,x,show} ...
CRiu Image Tool
CRiu Image Tool
positional arguments:
positional arguments:
{decode,encode} decode/encode - convert criu image from/to binary type
{decode,encode,info,x,show}
Use crit CMD --help for command-specific help
decode convert criu image from binary type to json
encode convert criu image from json type to binary
info show info about image
x explore image dir
show convert criu image from binary to human-readable json
optional arguments:
optional arguments:
-h, --help show this help message and exit
-h, --help show this help message and exit
</pre>
</pre>
=== Pretty output ===
=== Pretty output ===
Command <decode> prints JSON text in one line. This can be read by any further JSON-aware tool for parsing. For human eyes it's more convenient to read JSON multi-line with indentation. CRIT can do this when using the <code>show</code> action or the <code>--pretty</code> option.
Wend doing pretty optput CRIT does a little bit more, than just multiline indented JSON.
; Addresses and registers
; Addresses and registers
: By default those a printed in decimal, but the "1.2.3.4" for v4 or "::1" for v6 can be seen in the --pretty mode.
: By default those a printed in decimal, but the "1.2.3.4" for v4 or "::1" for v6 can be seen in the --pretty mode.
; Symbolic names for flags
: Some known bit sets (e.g. MAP_PRIVATE, MAP_ANONYMOUS, etc. for vma->flags) are shown with names.
; Symbolic names for flags
; Device numbers
: Some known bits (e.g. MAP_PRIVATE, MAP_ANONYMOUS, etc. for vma->flags) can be shown with names.
: If the field is known to be of <code>dev_t</code> type, it's printed in the <code>major:minor</code manner
== Functionality ==
== Functionality ==