FS#4571 : dnsmasq-2.28-1 won't start

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!

FS#4571 - dnsmasq-2.28-1 won't start

Attached to Project: Arch Linux
Opened by Roman Kyrylych (Romashka) - Friday, 05 May 2006, 08:32 GMT
Last edited by Roman Kyrylych (Romashka) - Thursday, 09 November 2006, 00:19 GMT

Task Type	Bug Report
Category	Packages: Extra
Status	Closed
Assigned To	Paul Mattal (paul)
Architecture	not specified
Severity	Medium
Priority	Normal
Reported Version	0.7.1 Noodle
Due in Version	Undecided
Due Date	Undecided
Percent Complete
Votes	0
Private	No

Details

:: Starting DNS/DHCP Daemon
dnsmasq: Cannot set capabilities: Operation not permitted

This task depends upon

Closed by Paul Mattal (paul)
Friday, 24 November 2006, 13:13 GMT
Reason for closing: Fixed

Comments (12)
Related Tasks (0/0)

Comment by Jens Adam (byte) - Friday, 05 May 2006, 09:30 GMT

/etc/rc.conf -> MODULES=(... capability ...)

Comment by Roman Kyrylych (Romashka) - Friday, 05 May 2006, 12:56 GMT

Thanks! I remember that there was a notice on website about capabilities but didn't think that new dnsmasq (or dnsmasq with new kernel) require it.

Comment by eliott (cactus) - Saturday, 06 May 2006, 04:59 GMT

Appears that it should be fixed in more recent dnsmasq release...

debian-bugs-closed@lists.debian.org/2006-04/msg03778.html"> http://www.archivum.info/debian-bugs-closed@lists.debian.org/2006-04/msg03778.html

http://thekelleys.org.uk/dnsmasq/CHANGELOG -- bottom of the changelog talks about no longer using capabilities.

Comment by Roman Kyrylych (Romashka) - Monday, 08 May 2006, 09:29 GMT

Fixed in dnsmasq-2.31-1. Close this bug.

Comment by Judd Vinet (judd) - Thursday, 22 June 2006, 17:29 GMT

Re-opened by Jens Adams:

The new version does not need the capability module to start, but then it cannot run as the configured user (default: nobody). A install message might be a good idea.

Comment by Jonathan Frazier (wide-eye) - Sunday, 15 October 2006, 15:26 GMT

here's a patch for the example config that should clear it up.