upstart should notice "/etc" inode change
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
upstart (Ubuntu) |
Confirmed
|
Medium
|
Unassigned |
Bug Description
When one boots ubuntu with "/" using overlayfs, the overlay would typically be empty and not have RW "/etc/" overlay directory yet.
Upon writing to RO-base "/etc/", a RW "/etc" overlay directory will be created.
Since a RW "/etc" didn't exist before, the inotify watches are still watching the RO-base "/etc/" directory and thus not notifying upstart to reload configurations of job files as appropriate.
If the filesystem used as an overlay support inotify, than inotify events would be emitted on the RW "/etc" and thus upstart would monitor it after initctl reload-
If RW "/" overlay is created before upstart is run, than when RW "/etc/" overlay is created, the RW "/" does receive inotify event that "/etc" is created.
I am thus proposing to add a by-default a job that monitors all "/" events via file-bridge, and if it notices that "/etc" has been created, executes initctl reload-
Related bugs:
* bug 882147: overlayfs does not implement inotify interfaces correctly
Related branches
Changed in upstart (Ubuntu): | |
assignee: | nobody → Dmitrijs Ledkovs (xnox) |
status: | New → Confirmed |
importance: | Undecided → Medium |
description: | updated |
Changed in upstart (Ubuntu): | |
assignee: | Dimitri John Ledkov (xnox) → nobody |
17:34 < infinity> bdmurray: I'm not sure how xnox's fix to 1213925 is a fix at all. It would catch the first time /etc is modified, and no time after that. on-overlayfs case is a dpkg trigger that registers interest in /etc/init and forces a config reload.
17:35 < infinity> bdmurray: I still think the only sane fix for the upstart-