FS#59771 - [unbound] systemd unit file defaults to Type=simple but unbound forks

Attached to Project: Community Packages
Opened by Vladimir Panteleev (CyberShadow) - Thursday, 23 August 2018, 10:09 GMT
Last edited by Eli Schwartz (eschwartz) - Thursday, 23 August 2018, 13:39 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

The default behavior of unbound is to fork (its -d switch cancels that). However, the systemd unit file provided by Arch Linux[1] does not specify Type=forking. This causes it to fail to start properly (systemd thinks it exits shortly after starting, and attempts restarting it).

[1]: https://git.archlinux.org/svntogit/community.git/tree/unbound/trunk/service

The service was previously invoked with -d, however, the unit file was changed in July following  FS#59162 .

Additional info:
* package version(s):

unbound 1.7.3-4

* config and/or log files etc:

systemd log excerpt with current behavior:
https://dump.thecybershadow.net/3f37f15094fd5ca9e8e49e8249320b11/09%3A32%3A04-upload.txt

Steps to reproduce:
Simply attempting to start unbound with no further configuration is sufficient to reproduce this for me currently.
This task depends upon

Closed by  Eli Schwartz (eschwartz)
Thursday, 23 August 2018, 13:39 GMT
Reason for closing:  Duplicate
Additional comments about closing:   FS#59503 

Loading...