add section name for kresd remote control #58
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
I had trouble finding how to remotely control the `kresd` process, in [this discussion][1]. Reading other parts of the documentation, we would be led to believe that just starting another process would be sufficient, but it's not actually the case. By adding an extra header, I am hoping users will be clearly drawn towards that part of the documentation when looking for that feature. [1]: https://forum.turris.cz/t/how-to-flush-dns-cache-or-force-a-refresh/6615/7
|
I think I'd go for a more significant change instead: https://gitlab.labs.nic.cz/knot/knot-resolver/merge_requests/682 |
|
works for me, although "control sockets" is not immediately obvious to outsiders. novice Unix users will be "what is a socket?" or worse "BLANK" and just skip over. ;) but i'll take any improvement on docs. :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I had trouble finding how to remotely control the
kresdprocess, in this discussion. Reading other parts of the documentation, we would be led to believe that just starting another process would be sufficient, but it's not actually the case.By adding an extra header, I am hoping users will be clearly drawn towards that part of the documentation when looking for that feature.