[Bug 1035076] Re: dnscache resolvconf update script still accesses /etc/resolvconf/run/

Launchpad Bug Tracker 1035076 at bugs.launchpad.net
Fri Sep 7 22:05:09 UTC 2012


This bug was fixed in the package resolvconf - 1.67ubuntu2

---------------
resolvconf (1.67ubuntu2) quantal; urgency=low

  * Apply patch by MarianoAbsatz to remove remaining reference to
    /etc/resolvconf/run (LP: #1035076)
  * Update ppp hooks to also exit when passed
    /org/freedesktop/NetworkManager/PPP/* (LP: #994575)
 -- Stephane Graber <stgraber at ubuntu.com>   Fri, 07 Sep 2012 18:01:59 -0400

** Changed in: resolvconf (Ubuntu)
       Status: Fix Committed => Fix Released

-- 
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/1035076

Title:
  dnscache resolvconf update script still accesses /etc/resolvconf/run/

Status in “resolvconf” package in Ubuntu:
  Fix Released

Bug description:
  At some point what used to be /etc/resolvconf/run moved to
  /run/resolvconf.

  I don't know if this is because of some LSB requirement or what. The
  point is that there seems to be parts of ubuntu that long for the old
  location:

  
   $ sudo invoke-rc.d networking restart
   * Running /etc/init.d/networking restart is deprecated because it may not enable again some interfaces
   * Reconfiguring network interfaces...                                                                                                                   /etc/resolvconf/update.d/dnscache: 94: /etc/resolvconf/update.d/dnscache: cannot create /etc/resolvconf/run/dnscache_new.19373: Directory nonexistent
  run-parts: /etc/resolvconf/update.d/dnscache exited with return code 2
  ssh stop/waiting
  ssh start/running, process 19462

  I think that either the /etc/resolvconf/update.d/dnscache script
  should be patched taking this into account or we could create a
  symlink to the new location:

  
  sudo ln -s ../../run/resolvconf /etc/resolvconf/run

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1035076/+subscriptions




More information about the foundations-bugs mailing list