There is a misleading help note in /etc/sysconfig/network/dcp:
In there we can find the following:
# resolv.conf will also stay untouched when MODIFY_RESOLV_CONF_DYNAMICALLY
# in /etc/sysconfig/network/config is set to "no".
#
DHCLIENT_MODIFY_RESOLV_CONF="yes"
However, that is not true. If MODIFY_RESOLV_CONF_DYNAMICALLY is set to no, in /etc/sysconfig/network/config, and DHCLIENT_MODIFY_RESOLV_CONF is set to yes, it will still modify resolv.conf. And if the opposite were the case, it would not modify resolv.conf.
So only the setting in /etc/sysconfig/network/dhcp, ie. the DHCLIENT_MODIFY_RESOLV_CONF is responsible for dynamic modification of /etc/resolv.conf.
MODIFY_RESOLV_CONF_DYNAMICALLY, in /etc/sysconfig/network/config is ignored.
I’d report this as bug, but I’m not sure if it’s a bug in scripting, a “bug” in “documentation” (the comment), or something else…
Just report it against the ‘sysconfig’ package if possible and include
all the details as you have specified below. If it gets to the wrong
spot, as it could apply to several potentially, the developers will sort
it out. If ‘sysconfig’ isn’t an option for the bug try Yast or perhaps
something DHCP-related.
Good luck.
Zonei wrote:
> There is a misleading help note in /etc/sysconfig/network/dcp:
>
> In there we can find the following:
>
>
> Code:
> --------------------
>
> # resolv.conf will also stay untouched when MODIFY_RESOLV_CONF_DYNAMICALLY
> # in /etc/sysconfig/network/config is set to “no”.
> #
> DHCLIENT_MODIFY_RESOLV_CONF=“yes”
>
> --------------------
>
>
> However, that is not true. If MODIFY_RESOLV_CONF_DYNAMICALLY is set to
> no, in /etc/sysconfig/network/config, and DHCLIENT_MODIFY_RESOLV_CONF is
> set to yes, it will still modify resolv.conf. And if the opposite were
> the case, it would not modify resolv.conf.
>
> So only the setting in /etc/sysconfig/network/dhcp, ie. the
> DHCLIENT_MODIFY_RESOLV_CONF is responsible for dynamic modification of
> /etc/resolv.conf.
>
> MODIFY_RESOLV_CONF_DYNAMICALLY, in /etc/sysconfig/network/config is
> ignored.
>
> I’d report this as bug, but I’m not sure if it’s a bug in scripting, a
> “bug” in “documentation” (the comment), or something else…
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org