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#39498 - [dnscrypt-proxy] Add support to multiple configurations/daemons

Attached to Project: Community Packages
Opened by Roger Duran (roger) - Monday, 17 March 2014, 12:13 GMT
Last edited by Felix Yan (felixonmars) - Sunday, 22 June 2014, 15:43 GMT
Task Type Feature Request
Category Packages
Status Closed
Assigned To Felix Yan (felixonmars)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
To connect to more than one dns, more instances are needed

Additional info:
In the patch, it uses /etc/conf.d/dnscrypt-proxy.[name], to start with systemctl start dnscrypt@name, i don't know if it's better to create a directory there and use *.conf files, like openvpn does.
   dnscrypt-proxy.service.patch (0.8 KiB)
This task depends upon

Closed by  Felix Yan (felixonmars)
Sunday, 22 June 2014, 15:43 GMT
Reason for closing:  Won't implement
Comment by Felix Yan (felixonmars) - Tuesday, 18 March 2014, 08:54 GMT
Actually other distros ship the package with no configurations at all (upstream default), or provide only one as us (like openwrt). I don't really think too many people will need to use two different DNS server either.

The patch at its current form cannot be accepted, since it breaks all current installs (the file /etc/conf.d/dnscrypt-proxy would not work). I'd rather suggest you keep the modified service file in /etc/ to fill your needs, and the bad situation of configuration profile support is really an upstream issue.

Loading...