Community Packages

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#54476 - [unbound] unbound.service should start before network-online.target and nss-lookup.target

Attached to Project: Community Packages
Opened by Pascal Ernster (hardfalcon) - Friday, 16 June 2017, 14:33 GMT
Last edited by Gaetan Bisson (vesath) - Tuesday, 27 June 2017, 16:56 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Gaetan Bisson (vesath)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

unbound.service should start before network-online.target and nss-lookup.target so other units can depend upon the predefined targets "network-online.target" and "nss-lookup.target" without having to know about specific DNS resolving daemons like unbound or resolved.

The fix consists of adding the following two lines to the [Unit] section of unbound.service:

Before=network-online.target nss-lookup.target
Wants=nss-lookup.target

A similiar fix has recently been committed upstream for systemd-resolved:

https://github.com/systemd/systemd/commit/3e06055500755053050620a45236ef606507e1bd

Fixing this bug will also make unbound.service comply with systemd documentation/specification:

https://www.freedesktop.org/software/systemd/man/systemd.special.html#nss-lookup.target
This task depends upon

Closed by  Gaetan Bisson (vesath)
Tuesday, 27 June 2017, 16:56 GMT
Reason for closing:  Fixed
Additional comments about closing:  unbound-1.6.3-3 in [testing]

Loading...