Skip to content
Snippets Groups Projects
Commit db74ba2d authored by Vladimír Čunát's avatar Vladimír Čunát
Browse files

Merge !484: doc: move kresd.systemd to section 7

parents 4db13a66 23c8ffbf
Branches
Tags
1 merge request!484doc: kresd.systemd belongs in section 7 of the manual
Pipeline #32805 failed with stages
in 9 minutes and 55 seconds
......@@ -5,7 +5,7 @@ Incompatible changes
--------------------
- systemd: change unit files to allow running multiple instances,
deployments with single instance now must use `kresd@1.service`
instead of `kresd.service`; see kresd.systemd(8) for details
instead of `kresd.service`; see kresd.systemd(7) for details
- systemd: the directory for cache is now /var/cache/knot-resolver
- unify default directory and user to `knot-resolver`
- directory with trust anchor file specified by -k option must be writeable
......
......@@ -1012,7 +1012,7 @@ The watchdog process must notify kresd about active file descriptors, and kresd
The daemon also supports `systemd socket activation`_, it is automatically detected and requires no configuration on users's side.
See ``kresd.systemd(8)`` for details.
See ``kresd.systemd(7)`` for details.
Enabling DNSSEC
===============
......
......@@ -164,7 +164,7 @@ Show short commandline option help.
.B \-V
Show the version.
.SH "SEE ALSO"
\fIkresd.systemd(8)\fR,
\fIkresd.systemd(7)\fR,
\fIhttps://knot-resolver.readthedocs.io\fR
.SH "AUTHORS"
.B kresd
......
.TH "kresd.systemd" "8" "2018-01-30" "CZ.NIC" "Knot DNS Resolver Systemd Units"
.TH "kresd.systemd" "7" "2018-01-30" "CZ.NIC" "Knot DNS Resolver Systemd Units"
.\"
.\" kresd.systemd.8 -- man page for systemd units for kresd
.\" kresd.systemd.7 -- man page for systemd units for kresd
.\"
.\" Copyright (c) 2018, CZ.NIC. All rights reserved.
.\"
......
......@@ -9,7 +9,7 @@ sd_listen_fds_with_names(3)).
Usage and Configuration
-----------------------
See kresd.systemd(8) for details.
See kresd.systemd(7) for details.
Manual activation
-----------------
......
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment