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#55688 - [dingo] is not configurable

Attached to Project: Community Packages
Opened by Nikolay Arhipov (nikarh) - Wednesday, 20 September 2017, 11:44 GMT
Last edited by Eli Schwartz (eschwartz) - Wednesday, 20 September 2017, 13:01 GMT
Task Type Feature Request
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:

"dingo" cli accepts a number of command line flags, but dingo systemd service is not configurable and uses default. One of those defaults is a port on which dingo listens - 32000. As a consequence to use dingo as a DNS server (in resolv.conf) user has to do port forwarding to 53 or edit systemd service located in /usr/lib. Both ways are quirky.

Please add a way to configure it.

Additional info:
* version: 0.13-2

This task depends upon

Closed by  Eli Schwartz (eschwartz)
Wednesday, 20 September 2017, 13:01 GMT
Reason for closing:  Not a bug
Additional comments about closing:  systemd drop-ins are a thing
Comment by Eli Schwartz (eschwartz) - Wednesday, 20 September 2017, 12:41 GMT
In what way is it not configurable, and what would you like to do about that?

All systemd units are configurable as a matter of course, see e.g. `systemctl edit` and the documentation for drop-ins in systemd.unit(5) -- what is so special about this one?
Comment by Nikolay Arhipov (nikarh) - Wednesday, 20 September 2017, 13:00 GMT
Thank you for pointing that, you can close this task.

Loading...