Community Packages

Please read this before reporting a bug:
http://wiki.archlinux.org/index.php/Reporting_Bug_Guidelines

Do NOT report bugs when a package is just outdated, or it is in Unsupported. 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#63044 - [unbound] 1.9.2-1 Is it somewhat preferable to have a /run/unbound dedicated directory?

Attached to Project: Community Packages
Opened by regid (regid1) - Sunday, 30 June 2019, 16:15 GMT
Task Type Feature Request
Category Packages
Status Unconfirmed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No

Details

With 1.9.2-1, the default pidfile is /run/unbound.pid.
Would it be a bit better to have a dedicated directory under /run, dedicated to unbound?
This will make /run a bit tidier. And /run/unbound seems to me a natural place for
control-interface: /run/unbound/unbound.sock
and maybe other files.

Can PKGBUILD configure
--with-pidfile=/run/unbound/unbound.pid \
?

It could be that apache2, and perhaps more packages, have a similar approach.
This task depends upon

Loading...