Arch Linux

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!
Tasklist

FS#35601 - Resolveconf generates an invalid resolv.conf file with extra commas

Attached to Project: Arch Linux
Opened by Harsh Gupta (Geotarget) - Sunday, 02 June 2013, 08:38 GMT
Last edited by Dave Reisner (falconindy) - Tuesday, 04 June 2013, 17:29 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture i686
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

I'm on Arch Linux, the latest version as of 2013 June 02.

Resolveconf generates an invalid "/etc/resolv.conf" file with entries as follows:

nameserver 123.123.123.123,
nameserver 123.123.123.123

As you can see the commas are unnecessary, and it breaks "pacman" updating, although ping works. This is because the network config is okay, but pacman apparently uses the "resolv.conf" data and the commas confuse it.

Please stop adding commas to the "resolv.conf" file since this breaks important features on Arch Linux.

I'm using the "netctl" network manager with a network static IP config file. I'm using multiple nameservers in the config file as follows: (not real data)

DNS=('123.123.123.0', '123.123.123.1')
This task depends upon

Closed by  Dave Reisner (falconindy)
Tuesday, 04 June 2013, 17:29 GMT
Reason for closing:  Not a bug
Comment by Allan McRae (Allan) - Sunday, 02 June 2013, 09:03 GMT
Don't use a comma in your DNS= line.
Comment by Harsh Gupta (Geotarget) - Monday, 03 June 2013, 09:50 GMT
I've manually edited it to make it work, but it says on the top "Generated by resolveconf", and it keeps overwriting my changes. I don't know specifically which program generates it but I assume that the authors do. I had to write protect the file to make it work.
Comment by Allan McRae (Allan) - Monday, 03 June 2013, 10:58 GMT
Did you try what I told you? Editing your DNS line in the netctl config file (netctl.profile I think)?
Comment by Harsh Gupta (Geotarget) - Tuesday, 04 June 2013, 12:20 GMT
Oh I'll try that, so you're saying its my mistake and not a bug that can be corrected? If its corrected then other people will not get the same error again...
Comment by Dave Reisner (falconindy) - Tuesday, 04 June 2013, 17:29 GMT
> If its corrected then other people will not get the same error again...
There's nothing to correct here except your understanding of the syntax. Config file parsers should not implement leniency under the expectation that users will fudge what's legitimately acceptable. As documented in netctl.profile(5):

"The files consist of variable definitions following the bash shell syntax"

Loading...