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 in 'Disable systemd socket activation' section.

szemley 2020-12-30 13:17:32 +00:00
parent 4ee35142a8
commit 5577e5155b
1 changed files with 11 additions and 12 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

23
systemd.md

@ -177,7 +177,7 @@ sudo systemctl stop dnscrypt-proxy.socket
sudo systemctl disable dnscrypt-proxy.socket
# Comment all systemd sockets options* found in both
# files and reload systemd configuration manager
# files and reload the systemd configuration manager
# to make sure systemd has read any changes
# (*e.g. `Also=dnscrypt-proxy.socket`)
# ---------------------------------------------------
@ -191,25 +191,24 @@ sudo systemctl daemon-reload
# -------------------------------------------------
sudo mousepad /etc/dnscrypt-proxy/dnscrypt-proxy.toml
# Restart DNSCrypt service and check if everything is okay
# (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.)
# ----------------------------------------------------------
# Restart DNSCrypt-Proxy service (of course,
# it's one of the most important command here)
# ---------------------------------------------
sudo systemctl restart dnscrypt-proxy.service
# Now, check if everything is okay (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.)
# --------------------------------------------------------
journalctl -u dnscrypt-proxy.service
systemctl status dnscrypt-proxy.service
```
**NOTE**: "_dnscrypt-proxy-resolvconf.service explicitly makes use of dnscrypt-proxy.socket_" (vide **ExecStart=** option etc.) but it seems, that this file is not needed when systemd socket activation is disabled. Anyway, it seems, that there is not any difference with `dnscrypt-proxy-resolvconf.service` enabled or not. It's up to you - you decide. A short discussion: see **2**.
**NOTE**: "_dnscrypt-proxy-resolvconf.service explicitly makes use of dnscrypt-proxy.socket_" (vide **ExecStart=** option etc.) 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. 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)`
--
Are you familiar with systemd? Please update this Wiki page with relevant information!