Changes

234 bytes added ,  10:17, 27 March 2019
Line 40: Line 40:     
; Device numbers
 
; Device numbers
: If the field is known to be of <code>dev_t</code> type, it's printed in the <code>major:minor</code manner
+
: 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 ==
Line 46: Line 46:  
=== Convert images to JSON and back ===
 
=== Convert images to JSON and back ===
   −
{{Status|ready}}
     −
This is the replacement for (rather nasty) criu show code. Also this is the way to edit the images before restoring from them.
+
This is the replacement for (rather nasty) <code>criu show</code> code. Also this is the way to edit the images before restoring from them.
    
It uses [https://developers.google.com/protocol-buffers/docs/reference/python/google.protobuf.text_format-module text_format] as a human-readable format for protobuf messages.
 
It uses [https://developers.google.com/protocol-buffers/docs/reference/python/google.protobuf.text_format-module text_format] as a human-readable format for protobuf messages.
Line 416: Line 415:     
=== Generate core files out of task images ===
 
=== Generate core files out of task images ===
  −
{{Status|ready}}
      
Moved into separate project called [[criu-coredump]].
 
Moved into separate project called [[criu-coredump]].
  −
=== On-the-fly conversion ===
  −
  −
{{Status|not ready}}
  −
  −
There's an idea to make CRIU spawn CRIT and read images "through" it, to allow for at-the-restore-time modifications
  −
  −
=== Convert between different image versions ===
  −
  −
{{Status|not ready}}
  −
  −
Right now we store the images version in inventory.img and collect info about [[what's bad with V1 images]]. If some day we have v2, CRIT will convert from v1. And for backward compatibility we'll use on-the-fly conversion when restoring from old images.
      
=== Show images statistics ===
 
=== Show images statistics ===
  −
{{Status|ready}}
      
E.g. -- total number of processes, files, memory, sockets, etc.
 
E.g. -- total number of processes, files, memory, sockets, etc.
Line 452: Line 435:  
;'mems'
 
;'mems'
 
:to show memory mappings info
 
:to show memory mappings info
 +
 +
== Planned functionality ==
 +
 +
=== On-the-fly conversion ===
 +
 +
There's an idea to make CRIU spawn CRIT and read images "through" it, to allow for at-the-restore-time modifications. For details, see https://github.com/xemul/criu/issues/59.
 +
 +
=== Convert between different image versions ===
 +
 +
Right now we store the images version in inventory.img and collect info about [[what's bad with V1 images]]. If some day we have v2, CRIT will convert from v1. And for backward compatibility we'll use on-the-fly conversion when restoring from old images.
    
=== Check/validate images ===
 
=== Check/validate images ===
  −
{{Status|not ready}}
      
Check that
 
Check that
 
* all images are present
 
* all images are present
 
* the inter-images IDs are in consistent state
 
* the inter-images IDs are in consistent state
 +
 +
For details, see https://github.com/xemul/criu/issues/44.
 +
 +
=== [[Anonymize image files]] ===
 +
 +
Since images contain raw memory dumps people may refuse to send us images for debugging. Need to anonymize them, i.e. -- remove this sensitive information.
    
[[Category:Images]]
 
[[Category:Images]]
 
[[Category:API]]
 
[[Category:API]]