Ubuntu
resolvconf package

resolvconf scripts are called for lo interface before resolvconf init script runs on boot

Bug #30492 reported by Someone
6
Affects Status Importance Assigned to Milestone
resolvconf (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

During boot the resolvconf's hook script 000resolvconf is called for from S08loopback. Because /dev/shm is not yet available (S11mountdevsubfs) and even resolvconf is not yet initialized (S38resolvconf) this produces an error "Error: /etc/resolvconf/run/interface is not a directory".

Revision history for this message
Roland Dreier (roland.dreier) wrote :

This happens for me with Dapper as well. In fact this causes a real problem, because eth0 is brought up before resolvconf has started. I have static nameserver information ("dns-nameservers" lines in /etc/network/interfaces), and since resolvconf fails, it doesn't get put in my resolv.conf. So I end up with an empty resolv.conf when booting finishes.

Revision history for this message
Sebastian Kapfer (caci) wrote :

Same bug as #33362.

Revision history for this message
Sebastian Kapfer (caci) wrote :

Should now be fixed in latest Dapper 1.34ubuntu2 .

Changed in resolvconf:
status: Unconfirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.