[Bug 933566] Re: Stopping resolvconf doesn't disable updates because Upstart doesn't run the pre-stop script
Thomas Hood
933566 at bugs.launchpad.net
Wed Feb 22 13:40:26 UTC 2012
> If and when that bug is fixed, the pre-stop script will
> have the exact same effect.
If and when the bug is fixed the wiki documentation at
http://upstart.ubuntu.com/wiki/Stanzas#pre-stop
should also be updated so that it no longer implies
(by omission, compared with post-stop) that the pre-stop
command isn't executed if the job fails to launch the
main process or the pre-start command fails.
** Summary changed:
- Stopping resolvconf doesn't disable updates
+ Stopping resolvconf doesn't disable updates because Upstart doesn't run the pre-stop script
** Changed in: upstart (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to resolvconf in Ubuntu.
https://bugs.launchpad.net/bugs/933566
Title:
Stopping resolvconf doesn't disable updates because Upstart doesn't
run the pre-stop script
Status in “resolvconf” package in Ubuntu:
Fix Released
Status in “upstart” package in Ubuntu:
Confirmed
Bug description:
Stopping the resolvconf job should disable updates by means of
deleting the enable-updates flag file, but this does not happen.
# ls -l /run/resolvconf
total 4
-rw-r--r-- 1 root root 0 2012-02-16 17:02 enable-updates
drwxr-xr-x 2 root root 60 2012-02-16 17:02 interface
-rw-r--r-- 1 root root 177 2012-02-16 17:02 resolv.conf
# stop resolvconf
stop: Unknown instance:
# ls -l /run/resolvconf
total 4
-rw-r--r-- 1 root root 0 2012-02-16 17:02 enable-updates
drwxr-xr-x 2 root root 60 2012-02-16 17:02 interface
-rw-r--r-- 1 root root 177 2012-02-16 17:02 resolv.conf
# start resolvconf
resolvconf start/running
# stop resolvconf
resolvconf stop/waiting
# ls -l /run/resolvconf
total 4
-rw-r--r-- 1 root root 0 2012-02-16 17:06 enable-updates
drwxr-xr-x 2 root root 60 2012-02-16 17:02 interface
-rw-r--r-- 1 root root 177 2012-02-16 17:02 resolv.conf
The following change seems to fix this.
--- /etc/init/resolvconf.conf_ORIG 2012-02-16 17:09:22.313489458 +0100
+++ /etc/init/resolvconf.conf 2012-02-16 17:08:31.398957282 +0100
@@ -14,6 +14,6 @@
resolvconf --enable-updates
end script
-pre-stop script
+post-stop script
resolvconf --disable-updates
end script
# stop resolvconf
resolvconf stop/waiting
# ls -l /run/resolvconf
total 4
drwxr-xr-x 2 root root 60 2012-02-16 17:02 interface
-rw-r--r-- 1 root root 177 2012-02-16 17:02 resolv.conf
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/933566/+subscriptions
More information about the foundations-bugs
mailing list