Difference between revisions of "Advanced usage"
Jump to navigation
Jump to search
(Created page with "This page describes non-standard options that can be useful when using crtools") |
(Evasive devices) |
||
| Line 1: | Line 1: | ||
This page describes non-standard options that can be useful when using crtools | This page describes non-standard options that can be useful when using crtools | ||
| + | |||
| + | == Evasive devices == | ||
| + | |||
| + | Sometimes an application opens a device file and then somehow the path by which it was opened becomes inaccessible (e.g. overmounted or unlinked). In that case crtools cannot easily dump and restore such a process. If you consider that the path doesn't really matter when dumping your apps state you can tell crtools that a device file can be opened by '''any''' name, even if the original one is no longer accessible. The option for that is <code>--evasive-devices</code> | ||
Revision as of 13:51, 18 September 2012
This page describes non-standard options that can be useful when using crtools
Evasive devices
Sometimes an application opens a device file and then somehow the path by which it was opened becomes inaccessible (e.g. overmounted or unlinked). In that case crtools cannot easily dump and restore such a process. If you consider that the path doesn't really matter when dumping your apps state you can tell crtools that a device file can be opened by any name, even if the original one is no longer accessible. The option for that is --evasive-devices