mirrors/dnscrypt-proxy
1
0
Fork 0
mirror of https://github.com/DNSCrypt/dnscrypt-proxy.git synced 2025-03-04 10:24:40 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions

Updated systemd (markdown)

szemley 2021-01-14 08:57:09 +00:00
parent 11fcff5b9a
commit 5f1ce602fc
1 changed files with 6 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

12
systemd.md

@ -163,11 +163,11 @@ sudo systemctl enable dnscrypt-proxy.service
### Disable systemd socket activation ### Disable systemd socket activation
In order to use DNSCrypt-Proxy but without systemd socket activation, 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, saying that systemd socket activaction is a better choice (for more informations, please check **1.** - these are various threads, that concern systemd and socket activation etc.) In order to use DNSCrypt-Proxy but without systemd socket activation, 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, saying that systemd socket activaction is a better choice (for more informations, please check **[1]** - there are various threads about systemd and socket activation etc.)
Anyway, disabling systemd socket activation is relative simple, not to say trivial. In short, everything is about stop and disable `dnscrypt-proxy.socket` unit, comment or remove options - related with systemd sockets - found in `dnscrypt-proxy.service` file (and eventually `dnscrypt-proxy-resolvconf.service`; see above examples [in:] **Usage with systemd**). The next step is to add a correct IP address to the `listen_addresses` option found in `dnscrypt-proxy.toml` configuration file. Finally, restart DNSCrypt-Proxy and then check service status. Anyway, disabling systemd socket activation is relative simple, not to say trivial. In short, everything is about to stop and disable `dnscrypt-proxy.socket` unit, comment or remove options - related with systemd sockets - found in `dnscrypt-proxy.service` file (and eventually `dnscrypt-proxy-resolvconf.service`; see above examples [in:] **Usage with systemd**). The next step is to add a correct IP address to the `listen_addresses` option found in `dnscrypt-proxy.toml` configuration file. Finally, restart DNSCrypt-Proxy and check service status.
Here are commands used to achieve above goal. (Please note that this method has been verified and tested. Furthermore, **mousepad** — a simple text editor was used, but it completely depends on Users preferences - just use your favorite editor). Here are commands used to achieve above goal. (Please note, that **mousepad** — a simple text editor was used, but it completely depends on User preferences - just use your favorite editor).
```sh ```sh
# Stop and disable socket units (it seems, # Stop and disable socket units (it seems,
@ -207,10 +207,10 @@ sudo systemctl restart dnscrypt-proxy.service
journalctl -u dnscrypt-proxy.service journalctl -u dnscrypt-proxy.service
systemctl status dnscrypt-proxy.service systemctl status dnscrypt-proxy.service
``` ```
**NOTE**: "_dnscrypt-proxy-resolvconf.service explicitly makes use of dnscrypt-proxy.socket_" (vide `ExecStart=` option) but it seems, that this file is not needed when systemd socket activation is disabled and there is no difference with `dnscrypt-proxy-resolvconf.service` enabled or not. A short discussion: see **2**. **NOTE**: "_dnscrypt-proxy-resolvconf.service explicitly makes use of dnscrypt-proxy.socket_" (vide `ExecStart=` option) but it seems, that this file is not needed when systemd socket activation is disabled and there is no difference with `dnscrypt-proxy-resolvconf.service` enabled or not. A short discussion: see **[2]**.
1. https://github.com/DNSCrypt/dnscrypt-proxy/issues?q=systemd+socket [1]. https://github.com/DNSCrypt/dnscrypt-proxy/issues?q=systemd+socket
2. https://github.com/DNSCrypt/dnscrypt-proxy/issues/1394 [2]. https://github.com/DNSCrypt/dnscrypt-proxy/issues/1394
-- --