On Dec 7, 2008, at 4:14 PM, David Cantrell wrote:
Jeremy Katz wrote:
On Dec 5, 2008, at 4:51 PM, David Cantrell wrote:
We have been writing the SEARCH= line to ifcfg files in network.py
for a while, but it only contains the domain we extract from the
FQDN. For users wanting to use the network service over NM, this
presents a problem because the SEARCH line present in the ifcfg
file will always override the information from the DHCP server.
If they're using NetworkManager, does it follow the logic to set up
the
search domains by default? If so, seems fine
NetworkManager doesn't seem to care about the SEARCH line if the ifcfg
file. It sets up resolv.conf as you change networks and it has its
own
handler for dhclient and it's own database of per-interface things
such
as the search list.
In ifcfg-reader.c, NM currently pulls in the SEARCH value and will use
it to some degree, but based on the comment in the code, it doesn't
look
like it will always do that. So I consider SEARCH to be ignored in
the
long run by NM. Removing it from the ifcfg file and having NM
enabled,
everything works fine. The only problems we are seeing right now are
the people that want to use the network service over NM and having the
SEARCH line in ifcfg overrides whatever dhclient gets back (which is
how
dhclient-script has worked for a long time).
Sounds sane
Jeremy
_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/anaconda-devel-list
