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#59503 - [unbound] systemd unit does not work
Attached to Project:
Community Packages
Opened by Mantas Mikulėnas (grawity) - Wednesday, 01 August 2018, 06:57 GMT
Last edited by Doug Newgard (Scimmia) - Thursday, 02 August 2018, 17:25 GMT
Opened by Mantas Mikulėnas (grawity) - Wednesday, 01 August 2018, 06:57 GMT
Last edited by Doug Newgard (Scimmia) - Thursday, 02 August 2018, 17:25 GMT
|
DetailsIn community-testing/unbound 1.7.3-3, unbound's command line lost the -d (do not fork) flag; however, the service type remained set to the default (simple). This combination causes the service to stop as soon as unbound tries to fork/daemonize.
The service needs either the -d option back, or switch to Type=forking. (Pidfiles shouldn't be needed.) |
This task depends upon
Closed by Doug Newgard (Scimmia)
Thursday, 02 August 2018, 17:25 GMT
Reason for closing: Not a bug
Additional comments about closing: Config issue
Thursday, 02 August 2018, 17:25 GMT
Reason for closing: Not a bug
Additional comments about closing: Config issue
Comment by Doug Newgard (Scimmia) -
Thursday, 02 August 2018, 15:47 GMT
Sounds like an unmerged .pacnew file.
Comment by Mantas Mikulėnas (grawity) -
Thursday, 02 August 2018, 17:06 GMT
The problem is that my live Unbound configuration has so many differences from the example configuration that merging with vimdiff has become infeasible...