docs for daemon: better visibility for control sockets

• promote the part into a section
• move it right after the section about interactive CLI
• minor reformulations, location of the sockets, etc.
• fix location of the daemon-supervised anchor

assigned to @tkrizek

I had feedback that naming of these sections could be improved, but I had no idea how to better name them at that moment.

added 54 commits

• 426ad36a...c0aa2bfb - 51 commits from branch master
• ed929ce3 - docs for daemon: better visibility for control sockets
• c432b841 - daemon/README.rst: update doc with systemd integration info
• 833bdf8a - daemon/README.rst: fix spelling erros

Compare with previous version

I'm thinking we could rename Running supervised to Systemd integration and remove the first two paragraphs with general info about supervisors, since we provide only systemd files in upstream.

added 2 commits

• b8b0433c - daemon/README.rst: update doc with systemd integration info
• 00fb290b - daemon/README.rst: fix spelling erros

Compare with previous version

mentioned in merge request knot-dns!941 (merged)

Text looks good, let's think more about structure/chapter ordering.

added 6 commits

• 00fb290b...44c9b7fb - 2 commits from branch master
• 95c5af25 - docs for daemon: better visibility for control sockets
• b2886c18 - daemon/README.rst: update doc with systemd integration info
• d9be265d - daemon/README.rst: fix spelling erros
• 817b720d - daemon/README.rst: split systemd integration into appropriate sections

Compare with previous version

added 1 commit

• 42355cf8 - daemon/README.rst: add warning about net.tcp_pipeline()

Compare with previous version

added 1 commit

• 55a6cc1f - fixup! daemon/README.rst: split systemd integration into appropriate sections

Compare with previous version

marked as a Work In Progress from 55a6cc1f

resolved all discussions

added 2 commits

• 4029b02e - daemon/README.rst: split systemd integration into appropriate sections
• da9ec240 - daemon/README.rst: add warning about net.tcp_pipeline()

Compare with previous version

unmarked as a Work In Progress

changed the description

merged

mentioned in commit 367a9070

Ah, the naming... I agree that "Control Sockets" might be a bit arcane term. Still, the suggested "Remote Control" doesn't sound correct to me, as I don't think there's anything remote – actually the unix sockets only work within localhost. I wonder if there's some standard terminology for means of controlling running services.