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

No more systemd examples

Frank Denis 2018-04-29 20:54:56 +02:00
parent 272e670b77
commit f861aec45f
1 changed files with 1 additions and 14 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

15
systemd.md

@ -2,9 +2,7 @@
`dnscrypt-proxy` can be started with systemd, and can also handle sockets created by systemd ("socket activation").
As a starting point, the source code contains a sample service file, as well as a socket configuration file: https://github.com/jedisct1/dnscrypt-proxy/tree/master/systemd
Packages from distribution repositories (e.g. Arch Linux) may also set up systemd sockets by default.
Packages from distribution repositories (e.g. Arch Linux) may set up systemd sockets by default.
In order to use systemd sockets, and only these, the `listen_addresses` property in the `dnscrypt-proxy` configuration file should be empty:
@ -12,17 +10,6 @@ In order to use systemd sockets, and only these, the `listen_addresses` property
listen_addresses = []
```
By default dnscrypt-proxy systemd service enables `DynamicUser` option for systemd 232+ which makes most of the filesystem viewed as read-only inside the service. That means all log and cache directories have to adjusted in `dnscrypt-proxy.toml` config file.
All log files should be put under `/var/log/dnscrypt-proxy/` directory, example:
```toml
log_file = '/var/log/dnscrypt-proxy/dnscrypt-proxy.log'
```
All cache files should be put under `/var/cache/dnscrypt-proxy/` directory, example:
```toml
cache_file = '/var/cache/dnscrypt-proxy/public-resolvers.md'
```
While using socket activation, following warnings are expected and can be safely ignored:
```