Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/index.php/Reporting_Bug_Guidelines

Do NOT report bugs when a package is just outdated, or it is in Unsupported. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#21453 - [netcfg] Make static /etc/resolv.conf configurable via RESOLV_CONF

Attached to Project: Arch Linux
Opened by Jesse Young (jlyo) - Sunday, 24 October 2010, 17:44 GMT
Last edited by Eric Belanger (Snowman) - Tuesday, 30 April 2013, 01:10 GMT
Task Type Feature Request
Category Arch Projects
Status Closed
Assigned To Jouke Witteveen (jouke)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

The user may not want netcfg to clobber their resolv.conf. Instead
allow the user to define where netcfg will output the generated
resolv.conf. Using dnsmasq is an example of this use case.

This patch only works for static IP addresses. I would like to add support for dhcp and ppp (and others?).
This task depends upon

Closed by  Eric Belanger (Snowman)
Tuesday, 30 April 2013, 01:10 GMT
Reason for closing:  Won't implement
Additional comments about closing:  netcfg has been moved to AUR
Comment by Jesse Young (jlyo) - Sunday, 24 October 2010, 21:15 GMT
As I am researching the resolv.conf hook in dhcpcd, I discovered the resolvconf utility (implemented in the community/openresolv package). I will look into integrating this tool into netcfg as an optional dependency.
Comment by Jesse Young (jlyo) - Monday, 25 October 2010, 03:18 GMT
Ok, here is a patch for running resolvconf rather than overwriting /etc/resolv.conf in case resolvconf exists. It looks like the semantics in dhcpcd as well as openvpn don't give the user an option turn off resolvconf if it exists. Calling resolvconf with a default configuration should give the same results as writing to /etc/resolv.conf directly if my understanding is correct.

Use this patch instead of the earlier one.

Thanks,
Jesse
Comment by Rémy Oudompheng (remyoudompheng) - Wednesday, 01 June 2011, 05:29 GMT
People might have resolvconf installed without using it. I'd prefer having some option array, like "OPTIONS=(resolvconf)" to indicate that a profile should use resolvconf instead of writing to /etc/resolv.conf
Comment by Jesse Young (jlyo) - Wednesday, 01 June 2011, 22:45 GMT
If resolvconf is left to its default configuration, then it does nothing except to push the $DOMAIN, $SEARCH, $DNS1 and $DNS2 to the top of the file, and pops them when the profile is disabled. The case without resolvconf has netcfg clobber /etc/resolv.conf without restoring it on profile shutdown. Basically its a library, rather than a separate utility, to make network managers more "nice", so to speak, to /etc/resolv.conf.

Having the default to use resolvconf if it exists parallels the behavior of dhcpcd, which does the same thing.

Loading...