FS#7024 - check that resolv.conf doesnt get clobbered by dhcpcd
Attached to Project:
Arch Linux
Opened by James Rayner (iphitus) - Sunday, 29 April 2007, 10:22 GMT
Last edited by James Rayner (iphitus) - Monday, 10 December 2007, 23:10 GMT
Opened by James Rayner (iphitus) - Sunday, 29 April 2007, 10:22 GMT
Last edited by James Rayner (iphitus) - Monday, 10 December 2007, 23:10 GMT
|
Detailslook at -R option.... manpage.
|
This task depends upon
Closed by James Rayner (iphitus)
Monday, 10 December 2007, 23:10 GMT
Reason for closing: Implemented
Monday, 10 December 2007, 23:10 GMT
Reason for closing: Implemented
say for example, uses the options for their own dns in a network profile, but uses dhcpcd to get an IP. dhcpcd will clobber the existing custom resolv.conf.
I added this as a reminder, as it is a bug in the new network scripts. I'm allowed to file bugs on my own work right? Thought i will be more descriptive in future.
James
This is for a network PROFILE. This is part of the new network profile system.
in network profiles, you may explicitly set DNS, to be used instead of what dhcpcd pulls in. As it is, dhcpcd is clobbering the explicitly set dns in the profile.
Explicit dns is useful, for when you say, don't want the dns from dhcpcd. Or want to add extra entries to your resolv.conf.
James
Let's not get all up in arms until we know exactly what James is doing.
And because you think it's silly to have a script do it... here's an example that makes it realistic: let's imagine "myprofile" has all the standard network setup, but then I specify 2 nameservers as part of that profile. Are you telling me that specifying nameservers isn't information enough with relation to not overwriting resolv.conf?