Intrepid: resolvconf interface cleanup fails during boot.

Bug #264165 reported by seeker5528 on 2008-09-03
This bug affects 10 people
Affects Status Importance Assigned to Milestone
resolvconf (Ubuntu)

Bug Description

On intrepid using resolvconf 1.42ubuntu1. Early in the boot process I see a message that resolvconf failed to delete /etc/resolvconf/run/interface/ Or whatever interfaces have been active when last booted and have dns-nameservers entries in the /etc/network/interfaces file.

The reason given for the failure is because the filesystem is read only.

seeker5528 (seeker5528) on 2008-09-03
description: updated

Problem seems in too early startup of resolvconf in boot process (S07 in rc.S).
I just moved S07resolvconf in S39resolvconf in /etc/rc.S and it works (at least at boot).
Needs to find a proper position in startup sequence.

mbeccaria (massibeccaria) wrote :

Same problem observed by me. In addition to the problem concerning the removal of /etc/resolvconf/run/interface/Network Manager I observe also another error, when the boot sequence claims it cannot create the /etc/resolvconf/run/enable-updates (still again due to read only file system ???)

Henry S. (snowball2050-gmail) wrote :

I'm having the same issue just like mbeccaria

Changed in resolvconf:
status: New → Confirmed
dcam (david-pastornet) wrote :

I can confirm this too....there's a screenshot of what I see at

Max Bowsher (maxb) wrote :

Strange, this change of start level is an Ubuntu delta from Debian:

diff -ru resolvconf-1.43/debian/rules resolvconf-1.43ubuntu1/debian/rules
--- resolvconf-1.43/debian/rules 2008-02-12 20:52:48.000000000 +0000
+++ resolvconf-1.43ubuntu1/debian/rules 2008-12-08 02:00:22.000000000 +0000
@@ -27,7 +27,7 @@
        dh_installdocs README
- dh_installinit --no-start -- start 38 S . stop 89 0 6 .
+ dh_installinit --no-start -- start 07 S .
        dh_installppp --name=000resolvconf
        install --mode=0755 debian/resolvconf.000resolvconf.ifupdown.if-up $(DESTDIR)/etc/network/if-up.d/000resolvconf
        install --mode=0755 debian/resolvconf.resolvconf.ifupdown.if-down $(DESTDIR)/etc/network/if-down.d/resolvconf

Now, the removal of the stop clause is mentioned in the debian/changelog, but the change of start level is _not_ mentioned. Mysterious.

A bit of historical spelunking on narrows it down to being introduced in Dapper, apparently in relation to bug 33362.

I still have the same problem like mbeccaria. Is there any solution for this? Apart from removing resolvconf?

data (yavor-dobrev) wrote :

I can confirm this too.

data (yavor-dobrev) wrote :

For me changing /etc/rc.S/S07resolvconf to S39resolvconf seems to resolve the issue without any (immediate) side effects.

amid1999 (amidsin1999) wrote :

Same problem for me, changing start order also helps.

I have the same problem under 9.04 and it causes that my PC gets the wrong nameserver (localhost instead of my router's IP) cutting me off the internet as long as I don't change /etc/resolv.conf to my router-IP, which gets erased after every reboot.

So I want to change start order -- but I don't know how. Can somebody please tell me what to do? TIA.

Thomas Hood (jdthood) wrote :

A new Ubuntu resolvconf package has been prepared by the Debian maintainers which we hope will fix this bug.

I ask you to test this new package before we upload it to the Ubuntu repos.

Please install the resolvconf package from ppa:jdthood/resolvconf ( and let me know whether or not you have any problems with it.
Thomas Hood
Debian resolvconf maintainers
<email address hidden>

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers