> But don't make that change, because then updates are not enabled after
> reboot!
Well, it looks like the change may be per se correct, and you simply have
something amiss on your system that's causing the resolvconf job to fail at
startup. It doesn't fail for me.
> it looks to me as if resolvconf is both started and stopped on boot,
> except that pre-stop scripts are not run. Or something. I don't
> understand Upstart.
This looks to me like a previously unreported bug in upstart.
resolvconf is the only job on my system which tries to use pre-start +
pre-stop without a main process. Conceptually, I think there's no
reason not to use post-stop since the post-stop script is run before the
stopped event is emitted, so I'll go ahead with committing this fix (but
not uploading until we know why resolvconf is failing to start for you
on boot).
Also raising a task on upstart, since I don't think the pre-stop script
should be silently skipped here.
** Changed in: resolvconf (Ubuntu)
Status: New => Triaged
** Changed in: resolvconf (Ubuntu)
Importance: Undecided => High
** Also affects: upstart (Ubuntu)
Importance: Undecided
Status: New
** Changed in: upstart (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/933566
Title:
Stopping resolvconf doesn't disable updates
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/933566/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
