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
Task Type Bug Report
Category Packages: Current
Status Closed
Assigned To James Rayner (iphitus)
Architecture All
Severity Low
Priority Normal
Reported Version 0.8 Voodoo
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

look at -R option.... manpage.
This task depends upon

Closed by  James Rayner (iphitus)
Monday, 10 December 2007, 23:10 GMT
Reason for closing:  Implemented
Comment by Glenn Matthys (RedShift) - Sunday, 05 August 2007, 14:15 GMT
What does archlinux have to do with this?
Comment by Roman Kyrylych (Romashka) - Sunday, 05 August 2007, 14:59 GMT
This task was created by James as a reminder to himself.
Comment by James Rayner (iphitus) - Monday, 06 August 2007, 02:03 GMT
and has everything to do with the arch network scripts.

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
Comment by Glenn Matthys (RedShift) - Monday, 06 August 2007, 04:25 GMT
But rewriting resolv.conf is dhcpcd's job! If some user doesn't want that, he or she should configure this in /etc/conf.d/dhcpcd.
Comment by James Rayner (iphitus) - Monday, 06 August 2007, 08:43 GMT
then tell me, why does dhcpcd have an option to not clobber resolv.conf?

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
Comment by Glenn Matthys (RedShift) - Monday, 06 August 2007, 14:18 GMT
Hmmz, /me is still against passing such options to dhcpcd with scripts, IMHO it will confuse people. Maybe just add a DHCP_OPTS="" to the network profile itself where the user can pass -R?
Comment by Aaron Griffin (phrakture) - Monday, 06 August 2007, 16:47 GMT
Man this is so silly - RedShift, I'm pretty sure this is here in relation to a scripting task.
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?

Loading...