Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#36795 - [openresolv] man resolvconf.conf incorrect about name_servers semantics
Attached to Project:
Arch Linux
Opened by Rulatir (Rulatir) - Thursday, 05 September 2013, 08:15 GMT
Last edited by Jan Alexander Steffens (heftig) - Sunday, 08 September 2013, 15:26 GMT
Opened by Rulatir (Rulatir) - Thursday, 05 September 2013, 08:15 GMT
Last edited by Jan Alexander Steffens (heftig) - Sunday, 08 September 2013, 15:26 GMT
|
DetailsI am not sure if this is a documentation bug or a resolvconf bug, but the actual effect of the name_servers option is different than documented:
man resolvconf.conf says: name_servers Prepend name servers to the dynamically generated list. What actually happens: Content of name_servers completely replaces the nameserver list. Before uncommenting the name_servers=127.0.0.1 line in /etc/resolvconf.conf the generated /etc/resolv.conf contains dynamically generated entries. After uncommenting said line, /etc/resolv.conf contains *only* nameserver 127.0.0.1 Additional info: * openresolv 3.5.6-1 |
This task depends upon
Closed by Jan Alexander Steffens (heftig)
Sunday, 08 September 2013, 15:26 GMT
Reason for closing: Upstream
Sunday, 08 September 2013, 15:26 GMT
Reason for closing: Upstream
Comment by Jan Alexander Steffens (heftig) -
Sunday, 08 September 2013, 15:26 GMT
Please bring this upstream: http://roy.marples.name/projects/openresolv/newticket