Updated systemd (markdown)

szemley 2020-08-12 17:09:11 +00:00
parent 89efaa800a
commit 4f82052c07

@ -165,7 +165,7 @@ sudo systemctl enable dnscrypt-proxy.service
In order to use DNSCrypt-Proxy without `systemd` socket activation, firstly User should consider various pros and cons. For example, main Developer - Mr Frank Denis suggests to not using `systemd` socket at all. On the other hand, some Users express their own opinions, suggesting that `systemd` socket activaction is a better choice (for more informations, please check **1.** - these are the threads, that concern `systemd` and socket activation etc.)
Anyway, disabling `systemd` socket activation is relative simple, not to say trivial. In short, this is about stopping/disabling `dnscrypt-proxy.socket` unit, commenting/removing options related with `systemd` sockets found in `dnscrypt-proxy.service` (and eventually `dnscrypt-proxy-resolvconf.service`) file - see above examples. Next, a proper address have to be added to the `listen_addresses` option found in the `dnscrypt-proxy.toml` configuration file. Finally, restart DNSCrypt service and check status.
Anyway, disabling `systemd` socket activation is relative simple, not to say trivial. In short, this is about stopping/disabling `dnscrypt-proxy.socket` unit, commenting/removing options related with `systemd` sockets found in `dnscrypt-proxy.service` (and eventually `dnscrypt-proxy-resolvconf.service`) file - see above examples (**Usage with systemd**). Next, a proper address have to be added to the `listen_addresses` option found in the `dnscrypt-proxy.toml` configuration file. Finally, restart DNSCrypt service and check status.
Here is an example of commands used to achieve above goal. (Please note, that this text was written, based on the experience with the Linux distribution with `systemd` support/enabled. Furthermore, **mousepad** — simple text editor was used, but it completely depends on Users preferences - just use your favorite editor).