*** This bug is a duplicate of bug 1385010 ***
https://bugs.launchpad.net/bugs/1385010
> did not know I am stepping on your toe here
No toes being stepped on here.
> had to take care of this, so I generate the resolv.conf from a package
- no link anymore
OK. Leave the resolvconf package ins
Uuh, Thomas - did not know I am stepping on your toe here. Pardon!
So, your hints where quite helpful as I did not notice the file being
updated was the one in /run/resolvconf.
My situation is this:
- 4 Racks of boxes with 1 to 3 networks each
- network 1 is static, the other 2 dhcp
- resolver c
I wrote:
> The proper way for the admin to stop /etc/resolv.conf from
> being updated by resolvconf is for him or her to remove the
> symbolic link /etc/resolv.conf -> ../run/resolvconf/resolv.conf.
HeinMueck wrote:
> what you describe as the proper way will not work at all
>- take a look at /etc/
Thomas,
what you describe as the proper way will not work at all - take a look
at /etc/network/if-up.d/000resolvconf. It only checks if
/sbin/resolvconf exists and if it is executable. As it does not check
for resolv.conf being a symlink it will never stop if it is not. If it
is supposed to be lik
The proper way for the admin to stop /etc/resolv.conf from being updated
by resolvconf is for him or her to remove the symbolic link
/etc/resolv.conf -> ../run/resolvconf/resolv.conf. The resolvconf
program only ever writes to the target of that symlink. Thus, in the
absence of that link, resolvcon
