InotifyOptions
From Linux Checkpoint / Restart Wiki
(Difference between revisions)
(Created page with 'Three options for dealing with inotify are: * Don't support it. We don't support it now, and reliably fail checkpoint. * Translate inodes being watched to pathnames at checkp…') |
m |
||
| (2 intermediate revisions by one user not shown) | |||
| Line 1: | Line 1: | ||
| + | '''Inotify and checkpoint/restart''' | ||
| + | |||
Three options for dealing with inotify are: | Three options for dealing with inotify are: | ||
| − | + | # Don't support it. | |
| − | + | ## This is what we're doing now. | |
| − | + | ## Checkpoint is refused with a helpful log message. | |
| + | # Translate inodes being watched to pathnames at checkpoint, and back at restart | ||
| + | # Use a filesystem which lets us restore inode numbers at restart. | ||
Latest revision as of 21:07, 19 February 2010
Inotify and checkpoint/restart
Three options for dealing with inotify are:
- Don't support it.
- This is what we're doing now.
- Checkpoint is refused with a helpful log message.
- Translate inodes being watched to pathnames at checkpoint, and back at restart
- Use a filesystem which lets us restore inode numbers at restart.
