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

Small changes.

szemley 2020-08-12 17:53:09 +00:00
parent 6f11d5a901
commit 55cf6887f8
1 changed files with 23 additions and 13 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

36
systemd.md

@ -167,41 +167,51 @@ In order to use DNSCrypt-Proxy without `systemd` socket activation, firstly User
Anyway, disabling `systemd` socket activation is relative simple, not to say trivial. In short, everything is about stopping and disabling `dnscrypt-proxy.socket` unit, commenting or removing options, related with `systemd` sockets, that are found in the `dnscrypt-proxy.service` file (and eventually `dnscrypt-proxy-resolvconf.service`) - see above examples [in:] **Usage with systemd**. The next step is to add the correct IP address to the `listen_addresses` option found in the `dnscrypt-proxy.toml` configuration file. Finally, restart DNSCrypt service and check the status.
Here is an example of commands used to achieve above goal. (Please note that this section was written based on the experience with the Linux distribution shipped with `systemd` support/enabled. Furthermore, **mousepad** — simple text editor was used, but it completely depends on Users preferences - just use your favorite editor).
Here is an example of commands used to achieve above goal. (Please note that this section was written based on the experience with the Linux distribution shipped with `systemd` support/enabled. Furthermore, **mousepad** — a simple text editor was used, but it completely depends on Users preferences - just use your favorite editor).
```
# Stop and disable socket unit
# -----------------------------
# (it seems, that `masking` is not needed)
# -----------------------------------------
sudo systemctl stop dnscrypt-proxy.socket
sudo systemctl disable dnscrypt-proxy.socket
# Comment/remove all socket-related (e.g. `dnscrypt-proxy.socket`)
# options and reload systemd manager configuration
# -----------------------------------------------------------------
# Comment all `systemd` sockets options* found in both
# files and reload `systemd` manager configuration
# to make sure `systemd` has read any changes
# * e.g. `Also=dnscrypt-proxy.socket`
# -----------------------------------------------------
sudo mousepad /lib/systemd/system/dnscrypt-proxy.service
sudo mousepad /lib/systemd/system/dnscrypt-proxy-resolvconf.service
sudo systemctl daemon-reload
# Edit configuration file and add a proper address
# to the `listen_address` option
# Edit configuration file and add an address to
# the `listen_address` option, e.g. '127.0.0.1:53'
# (however, it depends on User configuration)
# -------------------------------------------------
sudo mousepad /etc/dnscrypt-proxy/dnscrypt-proxy.toml
# Restart DNSCrypt service and check if everything is okay
# (there shouldn't be a `WARNING` or `FATAL` messages and
# information about wiring `systemd` sockets should be
# replaced with "Now listening on TCP/UDP" etc.)
# ---------------------------------------------------------
# (there shouldn't be any `WARNING` or `FATAL` messages and
# information about wiring `systemd` TCP/UDP sockets
# should be replaced with "Now listening on TCP/UDP" etc.)
# ----------------------------------------------------------
sudo systemctl restart dnscrypt-proxy.service
journalctl -u dnscrypt-proxy.service
systemctl status dnscrypt-proxy.service
```
**Note**: "_dnscrypt-proxy-resolvconf.service explicitly makes use of dnscrypt-proxy.socket_" (vide `systemctl show dnscrypt-proxy.socket` command in **ExecStart=** option etc.) but it seems, that this file is not needed with `systemd` socket activation and can be disabled. However, there is no difference when `dnscrypt-proxy-resolvconf.service` is enalbed and used or not. It's up to you - you decide. A short discussion is here: see **2**.
**Note**: "_dnscrypt-proxy-resolvconf.service explicitly makes use of dnscrypt-proxy.socket_" (vide `systemctl show dnscrypt-proxy.socket` command in **ExecStart=** option etc.) but it seems, that this file is not needed when `systemd` socket activation is disabled. However, there is no difference when `dnscrypt-proxy-resolvconf.service` is enalbed and used or not. It's up to you - you decide. A short discussion: see **2**.
1. https://github.com/DNSCrypt/dnscrypt-proxy/issues?q=systemd+socket
2. https://github.com/DNSCrypt/dnscrypt-proxy/issues/1394
For more informations about used commands, please check `man-pages`:
1. `systemctl(1)`
2. `journalctl(1)`
3. `systemctl(1)`
--
Are you familiar with systemd? Please update this Wiki page with relevant information!