Merge lp:~jamesodhunt/ubuntu/saucy/sysvinit/force-reload-configuration-for-broken-inotify into lp:ubuntu/saucy/sysvinit
Proposed by
James Hunt
Status: | Needs review |
---|---|
Proposed branch: | lp:~jamesodhunt/ubuntu/saucy/sysvinit/force-reload-configuration-for-broken-inotify |
Merge into: | lp:ubuntu/saucy/sysvinit |
Diff against target: |
29 lines (+11/-0) 2 files modified
debian/changelog (+7/-0) debian/src/sysv-rc/sbin/invoke-rc.d (+4/-0) |
To merge this branch: | bzr merge lp:~jamesodhunt/ubuntu/saucy/sysvinit/force-reload-configuration-for-broken-inotify |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Steve Langasek | Approve | ||
Review via email: mp+180690@code.launchpad.net |
Description of the change
* debian/
to work reliably on systems with broken inotify.
= Note =
The 'reload-
To post a comment you must log in.
Unmerged revisions
- 193. By James Hunt
-
debian/
src/sysv- rc/sbin/ invoke- rc.d: Call 'initctl reload- configuration'
to work reliably on systems with broken inotify.
Although the proposed change is safe for all systems, it is only currently necessary on systems where /etc/init/ is on overlayfs. As such, I wonder if we should be checking to see if /etc/init/ is actually on overlayfs prior to calling 'reload- configuration' (since on my system it took ~1 second to run 'reload- configuration' for the first time).
slangasek/smoser may have an opinion on this.