I installed unbound-1.4.14-1.fc16.x86_64 and attempted to start it. Startup hung for a long time and eventually failed, with this in the log:
Feb 8 20:05:43 hippogriff unbound: [12542:0] error: cannot open pidfile /var/run/unbound/unbound.pid: No such file or directory
Feb 8 20:05:43 hippogriff unbound: [12542:0] error: cannot chown 112.111 /var/run/unbound/unbound.pid: No such file or directory
The problem is that /run/unbound did not exist immediately after the package was installed. A call to systemd-tmpfiles --create was required to get it to exist, though I guess a reboot would have done it as well. This is because the directory is listed in the rpm but marked %ghost. Ghosting the directory causes the package to own it, but not to actually create it at install time.
The guidelines: https://fedoraproject.org/wiki/Packaging:Tmpfiles.d#Example_spec_file
indicate that the directory should not be %ghost'ed. It does say you can %ghost files that get created underneath that directory at runtime if you like, but it's not necessary.
*** Bug 797998 has been marked as a duplicate of this bug. ***
fix commited to unbound-1.4.16-2
unbound-1.4.16-2.fc16 has been submitted as an update for Fedora 16.
unbound-1.4.16-2.fc17 has been submitted as an update for Fedora 17.
* should fix your issue,
* was pushed to the Fedora 16 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing unbound-1.4.16-2.fc16'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
unbound-1.4.16-2.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.
unbound-1.4.16-2.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.