Difference between revisions of "What can change after C/R"
Jump to navigation
Jump to search
(+ mount ids) |
|||
| Line 1: | Line 1: | ||
| − | This page is very important (I believe). It describes what can change in a tasks' environment after a C/R cycle. If a software you're using depends on either item from the list below, it may break after C/R | + | This page is very important (I believe). It describes what can change in a tasks' environment after a C/R cycle. If a software you're using depends on either item from the list below, it may break after C/R. The list is incomplete, but we do our best to make it contain relevant data. |
; Per-task statistics | ; Per-task statistics | ||
| Line 12: | Line 12: | ||
; Mount points IDs | ; Mount points IDs | ||
: The numbers from first 2 columns of <code>/proc/$pid/mountinfo</code> | : The numbers from first 2 columns of <code>/proc/$pid/mountinfo</code> | ||
| + | |||
| + | ; Sockets IDs | ||
| + | : If you stat() a file descriptor with a socket the st_ino value can be used as unique socket ID. This value does changes after C/R as these IDs are global and we have no API to restore one. | ||
Revision as of 19:01, 26 November 2013
This page is very important (I believe). It describes what can change in a tasks' environment after a C/R cycle. If a software you're using depends on either item from the list below, it may break after C/R. The list is incomplete, but we do our best to make it contain relevant data.
- Per-task statistics
- Various counters, that can be obtained via
/proc/$pid/statusorgetrusage()
- Namespaces' IDs
- Numbers you see in the
/proc/$pid/ns/*links' targets
- Process start time
- It's in the 22nd field of the
/proc/$pid/statfile
- Mount points IDs
- The numbers from first 2 columns of
/proc/$pid/mountinfo
- Sockets IDs
- If you stat() a file descriptor with a socket the st_ino value can be used as unique socket ID. This value does changes after C/R as these IDs are global and we have no API to restore one.