*** This bug is a duplicate of bug 366967 ***
https://bugs.launchpad.net/bugs/366967
Thomas Hood:
I must decline that this is fixed.
How my system is setup:
Ubuntu 12.04.3 LTS Server minimal installed.
I have booted a system without /etc/network/interfaces.
I created /etc/network/interfaces,
*** This bug is a duplicate of bug 366967 ***
https://bugs.launchpad.net/bugs/366967
Please post your /etc/network/interfaces.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/448095
Title:
*** This bug is a duplicate of bug 366967 ***
https://bugs.launchpad.net/bugs/366967
Good lord. Will someone please assign this stuff to someone? I need this
for openvpn to my work place. It has been open for several years
already
--
You received this bug notification because you are a
*** This bug is a duplicate of bug 366967 ***
https://bugs.launchpad.net/bugs/366967
This should be fixed already in 1.63ubuntu8, available in the Precise
repo.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 366967 ***
https://bugs.launchpad.net/bugs/366967
I'm reluctant to apply the PPA because I fear that if it breaks I will
not be able to recover. Could someone summarize/update the cli steps as
done by SvG in the past for 11.10 ? I've tried these manual
*** This bug is a duplicate of bug 366967 ***
https://bugs.launchpad.net/bugs/366967
Nevermind, the quickfix from GdP seems to have worked as is.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 366967 ***
https://bugs.launchpad.net/bugs/366967
Hi Miguel.
I would very much appreciate it if you and other contributors to this bug
thread would test the latest resolvconf package at
https://launchpad.net/~jdthood/+archive/resolvconf. This package is
*** This bug is a duplicate of bug 366967 ***
https://bugs.launchpad.net/bugs/366967
...just removing (apt-get purge resolvconf) the package fixes the
problem for me.
I don't need the /etc/resolv.conf file being dynamically modified.
Simply purge the package, remove the # this file is auto
*** This bug is a duplicate of bug 366967 ***
https://bugs.launchpad.net/bugs/366967
** This bug has been marked a duplicate of bug 366967
ifupdown-udev integration should be thought-out more thoroghly
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Bug present in 11.04 natty aswell.
Most of the times resolv.conf is empty expect for 2 remarked
generated-by-resolvconf lines.
Only about 1 of 10 reboots resolv.conf will get filled correctly with dns-*
data from the interfaces file.
Please fix this, correct dns info is pretty important for
Sander et al.,
I found a problem in the upstart config file from your resolvconf
patch:
start on ( virtual-filesystems and starting udev )
This makes a restart udev hang, because upstart waits for resolvconf
to finish, which will never happen, as it waits for the signal virtual-
filesystems,
The new package ppa2 does not work as expected in Maverick. After every
start I have to do a dpkg-reconfigure resolvconf. Otherwise
/etc/resolv.conf is a dead link. Then I have to restart networking an
NIS. This is very annoying. I thing the ppa1 was good.
--
resolvconf starts after ifupdown,
ppa2 only changed the postinst script, so the error should have been in
ppa1 too.
To what does /etc/resolv.conf point and does /var/run/resolvconf exist
after booting?
--
resolvconf starts after ifupdown, does not pick the dns-nameserver and
dns-search lines up from /etc/network/interfaces
I've put a fixed build of resolvconf for maverick on
https://launchpad.net/~jk/+archive/ubuntu-fixes (ppa:jk/ubuntu-fixes)
The package contains the changes made by Simon Huerlimann and Sander van
Grieken.
Source code is available via above PPA and
Jürgen, I installed your deb, but it fails to create the
/var/run/resolvconf directory. Also the /etc/resolv.conf symlink still
points to /etc/resolvconf/run/resolv.conf
output of dpkg -i :
Preparing to replace resolvconf 1.46ubuntu1 (using
resolvconf_1.46ubuntu1ppa1_all.deb) ...
Unpacking
Sander, looks like a bug inherited from the lucid package. The postinst
script must run resolvconf -i instead of resolvconf --enable-
updates. I'll upload a fixed package in a few minutes. (The current
package should work after start resolvconf, though).
--
resolvconf starts after ifupdown,
The new package is in ppa:jk/ubuntu-fixes now. postinst now runs
resolvconf -i if the run dir doesn't exist yet.
--
resolvconf starts after ifupdown, does not pick the dns-nameserver and
dns-search lines up from /etc/network/interfaces
https://bugs.launchpad.net/bugs/448095
You received this
Ok my bad :)
I never thought of the /etc/init.d initscripts as 'config' files (and I
guess no package marks them as such) so I extended this assumption to
the upstart scripts too..
Never really used the '-s' option, thanks for the tip.
--
resolvconf starts after ifupdown, does not pick the
/etc/init.d scripts are treated as configuration files too, as
specifically mandated by Debian Policy [1]. By default, all files in
/etc are marked as conffiles by Debhelper [2]. This is important for
whoever’s working on this bug, because you will need to write code to
specifically clean up the
I'm talking about the actual package Anders. Apparently the package
contents are incorrect at your [1] link.
$ dpkg -l | grep resolvconf
ii resolvconf 1.46ubuntu1
name server information handler
$ apt-cache showpkg
I'm talking about the actual package Anders. Apparently the package
contents are incorrect at your [1] link.
$ dpkg -l | grep resolvconf
ii resolvconf 1.46ubuntu1
name server information handler
$ apt-cache showpkg
As Anders said, conffiles don't get deleted by default.
Do 'dpkg -s resolvconf | grep /etc/init/', you should see that
/etc/init/resolvconf.conf is marked as obsolete.
--
resolvconf starts after ifupdown, does not pick the dns-nameserver and
dns-search lines up from /etc/network/interfaces
I just upgraded one of my systems to Maverick, and the bug seems to be
solved out-of-the-box there.
However, it seems that they just dropped in the upstart script from this bug
without much thinking, resulting in somewhat of a mutant resolvconf, because
a) the upstart script assumes the modified
Ehh? Changelog of resolvconf doesn't match reality?
Or am I looking in the wrong spot?
https://code.launchpad.net/~ubuntu-
branches/ubuntu/maverick/resolvconf/maverick
* Merge from debian unstable (LP: #605116), remaining changes:
- bin/resolvconf:
+ fail with non-zero exit code when
Sander van Grieken: I’m not sure what you’re talking about, there’s no
Upstart script in the Ubuntu resolvconf package [1]. Perhaps you
previously had the PPA package installed and it’s left over from that
(note that dpkg will not delete conffiles by default [2])?
[1]
Isn't Debian still planning on moving to upstart? If so that would be a
major vote of confidence and would guarantee upstart sticks around for a
while longer.
systemd looks very neat. That both RedHat and OpenSUSE are moving to
adopt it is telling but I don't think it's very likely Ubuntu will
My apologies, I have to backtrack on my prev statement. I thought to have read
that on LWN
some time in the past, but I cannot find such statement anymore through google.
Fact is, that Debian hasn't moved to upstart OR systemd (or initng for that
matter) yet,
even in unstable, and is using
On Wednesday 15 September 2010 19:27:47 Liraz wrote:
Many thanks to everyone who helped track down this regression, which
effected TurnKey Linux users of the new TurnKey Core Lucid-based beta as
well:
https://bugs.launchpad.net/turnkeylinux/+bug/596560
IMHO, for desktop usage upstart has
Many thanks to everyone who helped track down this regression, which
effected TurnKey Linux users of the new TurnKey Core Lucid-based beta as
well:
https://bugs.launchpad.net/turnkeylinux/+bug/596560
IMHO, for desktop usage upstart has great potential. But for servers
it's a net loss. Booting a
** Tags added: patch
--
resolvconf starts after ifupdown, does not pick the dns-nameserver and
dns-search lines up from /etc/network/interfaces
https://bugs.launchpad.net/bugs/448095
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
The next thing that needs to happen is that someone needs to propose a
debdiff for sponsorship
In that case, unsubscribing ubuntu-sponsors
--
resolvconf starts after ifupdown, does not pick the dns-nameserver and
dns-search lines up from /etc/network/interfaces
Fabrice, can you at least add an explanation why you unassigned MOTU?
Do you mean this bug will be a WONTFIX?
--
resolvconf starts after ifupdown, does not pick the dns-nameserver and
dns-search lines up from /etc/network/interfaces
https://bugs.launchpad.net/bugs/448095
You received this bug
No, just that bugs should not in general be assigned to MOTU. They
should be assigned to a specific person who is actively working on the
bug (if any). As you can see, the bug is still Confirmed.
The next thing that needs to happen is that someone needs to propose a
debdiff for sponsorship: a
** Changed in: resolvconf (Ubuntu)
Assignee: MOTU (motu) = (unassigned)
--
resolvconf starts after ifupdown, does not pick the dns-nameserver and
dns-search lines up from /etc/network/interfaces
https://bugs.launchpad.net/bugs/448095
You received this bug notification because you are a
Gabriel's quick fix (#57) didn't work for me. Bug #550962 (marked as a
duplicate of this bug) mentions adding
invoke-rc.d networking restart
to rc.local, so I'm going to try that. Rather frustrating, as this is
even more problematic in ubuntu server, where NetworkManager isn't even
an option.
Why not just install Simon's package?
--
resolvconf starts after ifupdown, does not pick the dns-nameserver and
dns-search lines up from /etc/network/interfaces
https://bugs.launchpad.net/bugs/448095
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
@Simon: Hopefully Debian will pickup the changes that cleanup the
hardcoded paths, but as I found out they don't use upstart, so those
parts will be useless to them. So we're stuck with MOTU :)
If I find the time I'll take another look at the packaging scripts, so
at least the symlink setup works
I'll try out and update how Simon's package does with ubuntu server
10.04 tomorrow.
--
resolvconf starts after ifupdown, does not pick the dns-nameserver and
dns-search lines up from /etc/network/interfaces
https://bugs.launchpad.net/bugs/448095
You received this bug notification because you
Here is my quick fix, it just moves resolvconf directory creation
earlier and disables invocation from rcS.d since the init.d script
doesn't support running twice:
sudo update-rc.d resolvconf disable
sudo tee /etc/init/earlier-resolvconf.conf 'EOF'
description Prepare resolvconf directory
@Jürgen: Oops, my bad. Thank you! Fixed PPA upload is on the way...
@Sander: Sounds very reasonable. I have a hard time really understanding
all the tests and checks the original postinst does:-( What you propose
sounds like a straight and clean solution. I'll probably won't find the
time to
Since I haven't been looking at this bug for a while, I'll just dump my
ideas of what IMO should be done in the postinst (and maybe other)
package scripts, before I forget them.
There's a couple of situations that should be handled:
a) installing resolvconf while being in a non-resolvconf state
resolvconf (1.45ubuntu1ppa5) karmic; urgency=low
* Use /var/run in resolvonf binary.
-- Simon Huerlimann (CyT) simon.huerlim...@cyt.ch Mon, 03 May 2010
00:27:16 +0200
Why RUN_DIR=${RESOLVCONF_RUNDIR:=/var/run}? Didn't you mean
/var/run/resolvconf?
That's what your postinst and apparmor
Ubuntu 10.04 : misbehaviour is still present. Hope to see resolvconf
better integrated with ifupdownupstart in the near future .
--
resolvconf starts after ifupdown, does not pick the dns-nameserver and
dns-search lines up from /etc/network/interfaces
https://bugs.launchpad.net/bugs/448095
You
@Sander: took much longer to find some time to fix the /lib/init/rw vs.
/var/lib bug. The postinst script is full of checks to handle all kinds
of setups. Not sure how much of that is really needed. But as I don't
get the idea of all of it, I just leave it. Regarding the comment in the
beginning
I just upgraded to lucid and installed your PPA package.
Of course I forgot to check the situation before installing your PPA
package, but anyway, I ended up with a different /etc/resolv.conf link.
A quick check reveals that the postinst script in the deb is
(re)creating the link to
Hi Sander
Thanks for the report. Will check, fix, release. (Hopefully... ;-)
--
resolvconf starts after ifupdown, does not pick the dns-nameserver and
dns-search lines up from /etc/network/interfaces
https://bugs.launchpad.net/bugs/448095
You received this bug notification because you are a
Thanks Simon for packaging this for Lucid, much appreciated.
My currently installed resolvconf package notes the following contacts as
maintainers:
Maintainer: Ubuntu MOTU Developers ubuntu-m...@lists.ubuntu.com
Original-Maintainer: resolvconf maintainers
@Ubunteros: can I do anything to get this in for Lucid? Look out for a
sponsor, do some bikesheding on the package, anything?
Lucid is a LTS release and expected to be more stable than other
releases. And this is a genuine regression compared to the last LTS. I
understand that resolvconf is in
Maybe someone with the necessary right could raise the importance of
this bug. I mean, this bug makes resolvconf doing DOS on LTS upgrades
from hardy, but even bug #60518 did get 'medium'.
I also did some bug triaging to make this one stand out more;-)
--
resolvconf starts after ifupdown, does
Simon: Your resolvconf “1.45ubuntu1ppa1” is actually version 1.44, which
seems … really odd. A patch that reverts all the changes between 1.44
and 1.45 as a side effect is certainly not going to make it into Lucid.
You’ll need to post a clean debdiff against the current Lucid package
with no
Andres: You're absolutely right. I've just created a correct karmic
package, but was in need for a fixed package for lucid an hour ago. My
fix was to just bump the package version to get it built on lucid.
Will work on an updated lucid package and repost. The karmic package
should be okay to
FYI, you can install a particular version of a package (even if it is a
downgrade) by running
sudo aptitude install resolvconf=1.44ubuntu1ppa2
There is no need to artificially inflate the package’s version number.
--
resolvconf starts after ifupdown, does not pick the dns-nameserver and
Anders: Thank you for the tip! A rebased version is currently
building/publishing in my PPA. Should soon be available.
Changes to 1.44ubuntu1ppa2:
* using 1.45ubuntu1 as base
* cleaning up debian/changelog to only have one new version
* using LP: instead of Closes: to close Launchpad bug, not
Mmh, just found a bug, please wait for ...ppa3 before testing. Sorry
--
resolvconf starts after ifupdown, does not pick the dns-nameserver and
dns-search lines up from /etc/network/interfaces
https://bugs.launchpad.net/bugs/448095
You received this bug notification because you are a member of
Okay, uploaded resolvconf-1.45ubuntu1ppa4 to my PPA. Will take a few
minutes 'till it's published.
Changes to resolvconf-1.45ubuntu1ppa2:
* added /sbin/resolvconf version by Sander van Grieken (which was forgotten in
last upload)
* updated postinst and prerm to directly use resolvonf to
** Patch added: Debdiff resolvconf-1.45ubuntu1 (lucid) =
resolvconf-1.45ubuntu1ppa4 (hPPA)
http://launchpadlibrarian.net/42426351/debdiff-1.45ubuntu1ppa4.diff
--
resolvconf starts after ifupdown, does not pick the dns-nameserver and
dns-search lines up from /etc/network/interfaces
I've created a resolvconf package incorporating the fixes to port
resolvconf to upstart from Sander van Grieken. It's available from my
PPA at https://launchpad.net/~huerlisi/+archive/ppa.
Please test if it works as expected and give feedback if not.
@Ubuntu guys: tell me what to do to enhance
Duplicate Bug #548576 reports this same problem in Kubuntu Lucid Lynx
Beta 1 amd64 daily disks of 2010-03-25 and 2010-03-27.
On this network, individual hosts are set up to use DHCP and individual
nameservers are not listed in /etc/network/interfaces. Predictable IP
addresses are assigned by the
Also affects me on a machine installed with Ubuntu Lucid Alternate AMD64
beta 1. On each start, the file /etc/resolv.conf is empty although dns-
servers are correctly specified in /etc/network/interfaces. If I run
sudo ifdown eth0 sudo ifup eth0, /etc/resolv.conf gets its normal
content from
Just to say I have this bug too. :(
Symptom:
After a reboot, /etc/resolv.conf contains only this:
$ cat /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 127.0.0.1
Yeah I'm actually stunned that such a design failure is not acted upon by
Ubuntu. Guess
they just capitalize on the work done by Debian, without having to do the hard
work of
actually maintaining a distribution.
However this bug MUST sting on servers and 'old-school' people that use
bug report about my case:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/500735
pppoeconf autoconnect does not work fully in ubuntu 9.10.
--
resolvconf starts after ifupdown, does not pick the dns-nameserver and
dns-search lines up from /etc/network/interfaces
Yes I thought that too, Universe is not the place for resolvconf.
But anyway, it seems no one from Ubuntu is interested in this bug?
--
resolvconf starts after ifupdown, does not pick the dns-nameserver and
dns-search lines up from /etc/network/interfaces
https://bugs.launchpad.net/bugs/448095
** Changed in: resolvconf (Ubuntu)
Assignee: (unassigned) = MOTU (motu)
--
resolvconf starts after ifupdown, does not pick the dns-nameserver and
dns-search lines up from /etc/network/interfaces
https://bugs.launchpad.net/bugs/448095
You received this bug notification because you are a
It feels somewhat strange that resolvconf is relegated to 'universe' in Ubuntu.
In Debian, its role is pretty infrastructural. And it is quite closely related
with ifupdown.
--
resolvconf starts after ifupdown, does not pick the dns-nameserver and
dns-search lines up from
ok, time for a full checklist :)
- update /sbin/resolvconf from bug attachment
- update /etc/resolvconf/update.d/libc from bug attachment
- install /etc/init/resolvconf.conf from bug attachment
- remove /etc/rcS.d/S07resolvconf
- make sure /etc/resolv.conf symlinks to
I think the problem is that there is a significant post-boot delay before
resolv.conf is updated. It took ~ 90sec (after gdm start) on last boot.
But at least it's working
+Reardon
On Mon, Dec 28, 2009 at 5:11 AM, Sander van Grieken san...@3v8.net wrote:
ok, time for a full checklist :)
-
Ok, I've tried with all your latest, and basically nothing has changed, it's
all still broken. On system boot, resolv.conf remains blank (or rather, it
is created, but with no entries, only the top comment lines).
ifdown/ifup fixes the problem. Same as the Ubuntu release problem.
Have you
Did you redownload the /sbin/resolvconf replacement? Can you confirm there are
no
differences between your copy and the attachment? Because you report the same
error the
first /sbin/resolvconf replacement I posted had, and I cannot reproduce your
current error
with the current one.
--
My mistake this time. It's working properly now with your updated
/sbin/resolvconf
+Reardon
On Sat, Dec 26, 2009 at 7:16 AM, Sander van Grieken san...@3v8.net wrote:
Did you redownload the /sbin/resolvconf replacement? Can you confirm there
are no
differences between your copy and the
Found one more tiny bug. fixed it and replaced /sbin/resolvconf
attachment.
** Attachment added: /sbin/resolvconf
http://launchpadlibrarian.net/37215643/resolvconf
** Attachment removed: replacement for /sbin/resolvconf
http://launchpadlibrarian.net/37141756/sbin.resolvconf
--
You should use the /sbin/resolvconf from #17. I made a stupid mistake in
the one I posted first.
There's no need to create /lib/init/rw/resolvconf/interface by hand. It
should be created at boot, or by calling /sbin/resolvconf -i as root.
--
resolvconf starts after ifupdown, does not pick the
** Attachment removed: replacement for /sbin/resolvconf
http://launchpadlibrarian.net/37130195/sbin.resolvconf
** Attachment removed: resolvconf.conf
http://launchpadlibrarian.net/37105983/resolvconf.conf
--
resolvconf starts after ifupdown, does not pick the dns-nameserver and
in my case also ping ya.ru does not work, but host ya.ru and then ping
ip address works.
--
resolvconf starts after ifupdown, does not pick the dns-nameserver and
dns-search lines up from /etc/network/interfaces
https://bugs.launchpad.net/bugs/448095
You received this bug notification because
Your solution did not work on reboot. Now when I try ''sudo resolvconf -i'
I get a different error
$ sudo resolvconf -i
mkdir: cannot create directory `': No such file or directory
resolvconf: Error: unable to create
+Reardon
On Fri, Dec 25, 2009 at 11:30 AM, Sander van Grieken san...@3v8.net
resolvconf.conf should be saved in /etc/init
--
resolvconf starts after ifupdown, does not pick the dns-nameserver and
dns-search lines up from /etc/network/interfaces
https://bugs.launchpad.net/bugs/448095
You received this bug notification because you are a member of Ubuntu
Bugs, which is
but still, this is probably not the bug you suffer from..
--
resolvconf starts after ifupdown, does not pick the dns-nameserver and
dns-search lines up from /etc/network/interfaces
https://bugs.launchpad.net/bugs/448095
You received this bug notification because you are a member of Ubuntu
Bugs,
I've tried your fix Sander and it sort of works. Which is to say that
resolvconf properly runs at boot. HOWEVER, it does not run correctly on
ifdown/ifup:
$ sudo ifdown eth0
[sudo] password for reardon:
resolvconf: Error: /lib/init/rw/resolvconf/interface is not a directory
resolvconf: Error:
I created the directory /lib/init/rw/resolvconf/interface by hand. But no
idea what should go in here. The whole point of installing resolvconf in
the first place was so that vpn clients would work properly (in my case,
vpnc). But no updates to resolv.conf are made when I connect with vpnc
Hmm yeah I wasn't really clear in my prev post.
It definately obsoletes the old sysv init script, which should be
removed.
The initialisation part is the most essential and moved to the upstart
script. The other actions on the init script are really nothing more
than calling (or not) 'update' on
Jürgen, you mean this should be the case in 9.10 or 10.04 ?
--
resolvconf starts after ifupdown, does not pick the dns-nameserver and
dns-search lines up from /etc/network/interfaces
https://bugs.launchpad.net/bugs/448095
You received this bug notification because you are a member of Ubuntu
hello. firefox and empathy do not work, though ping and host commands
work. my internet is set with pppoeconf and is set to connect
automatically. currently i fix this with sudo poff dsl-provider and then
sudo pon dsl-provider. what is better way?
probably this is because this bug.
--
by the way i was going to report bug , report bug link in
https://bugs.launchpad.net/ubuntu redirects to
https://help.ubuntu.com/community/ReportingBugs i tried to click that buttin in
firefox but it is going to send many unneeded things. impossibility to fill bug
report in site is quite big
q.dinar, probably not the same bug, since resolving works for you with
ping and host
--
resolvconf starts after ifupdown, does not pick the dns-nameserver and
dns-search lines up from /etc/network/interfaces
https://bugs.launchpad.net/bugs/448095
You received this bug notification because you
Ok I made the upstart script 'restartable', and unified more hardcoded
paths into /sbin/resolvconf
- the initialisation of the rundir can now be forced with /sbin/resolvconf -i,
and is automatically done by the upstart script when no valid structure is found
- starting and stopping the service
** Attachment added: replacement for /sbin/resolvconf
http://launchpadlibrarian.net/37130195/sbin.resolvconf
--
resolvconf starts after ifupdown, does not pick the dns-nameserver and
dns-search lines up from /etc/network/interfaces
https://bugs.launchpad.net/bugs/448095
You received this
** Attachment added: replacement for /etc/resolvconf/update.d/libc
http://launchpadlibrarian.net/37130232/etc.resolvconf.update.d.libc
--
resolvconf starts after ifupdown, does not pick the dns-nameserver and
dns-search lines up from /etc/network/interfaces
** Attachment added: new replacement for /sbin/resolvconf
http://launchpadlibrarian.net/37141756/sbin.resolvconf
--
resolvconf starts after ifupdown, does not pick the dns-nameserver and
dns-search lines up from /etc/network/interfaces
https://bugs.launchpad.net/bugs/448095
You received
i have tried to
in the file '/etc/init/network-interface.conf'
comment out the line 'exec ifup --allow auto $INTERFACE'
but in my case this has not helped.
Sander van Grieken, should i try your files? where is located
resolvconf.conf ?
--
resolvconf starts after ifupdown, does not pick the
Hi,
I made an upstart script, like Scott suggested, which initialises the
resolvconf directory structure. I have it start pre-udev, so it's sure
to fire before ifup. It replaces the sysv link in rcS.d, but I also made
some changes to resolvconf itself, basically I moved the resolvconf run
oh and symlink your /etc/resolv.conf to
/lib/init/rw/resolvconf/resolv.conf !
--
resolvconf starts after ifupdown, does not pick the dns-nameserver and
dns-search lines up from /etc/network/interfaces
https://bugs.launchpad.net/bugs/448095
You received this bug notification because you are a
resolvconf actually should already use /lib/init/rw/resolvconf with
/etc/resolvconf/run being a symlink to it. (At least for new
installations, for upgraded systems I had to fix this manually).
--
resolvconf starts after ifupdown, does not pick the dns-nameserver and
dns-search lines up from
I'm having difficulty understanding what this script accomplishes. If it
it co-exists with the existing init script, then when
'/etc/init.d/resolvconf start' does finally run, ${RUNDIR}/interface
will be deleted again, which is not what we wanted.
If it's meant to act as a replacement for the
** Tags added: regression-release
** Tags removed: regression-potential
--
resolvconf starts after ifupdown, does not pick the dns-nameserver and
dns-search lines up from /etc/network/interfaces
https://bugs.launchpad.net/bugs/448095
You received this bug notification because you are a member
The crude fix is usual, similar to LP:366967 :
in the file '/etc/init/network-interface.conf'
comment out the line 'exec ifup --allow auto $INTERFACE'
works for me and my resolvconf, so far.
--
resolvconf starts after ifupdown, does not pick the dns-nameserver and
dns-search lines up from
** Tags added: regression-potential
--
resolvconf starts after ifupdown, does not pick the dns-nameserver and
dns-search lines up from /etc/network/interfaces
https://bugs.launchpad.net/bugs/448095
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Obvious fix is to resolvconf, e.g. by porting to upstart you could
start on starting network-interface
** Changed in: ifupdown (Ubuntu)
Status: New = Won't Fix
--
resolvconf starts after ifupdown, does not pick the dns-nameserver and
dns-search lines up from /etc/network/interfaces
** Summary changed:
- On reboot, resolvconf does not pick the dns-nameserver and dns-search lines
up from /etc/network/interfaces. That means you have not DNS
+ resolvconf starts after ifupdown, does not pick the dns-nameserver and
dns-search lines up from /etc/network/interfaces
--
98 matches
Mail list logo
