From: Aleš Mrázek Date: Wed, 1 Mar 2023 15:19:52 +0000 (+0100) Subject: Delete gettingstarted-intro.rst X-Git-Tag: v6.0.1~11^2~1^2~5 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=22f2e7edf962ada789825536242f99ea3b0df570;p=thirdparty%2Fknot-resolver.git Delete gettingstarted-intro.rst --- diff --git a/doc/gettingstarted-intro.rst b/doc/gettingstarted-intro.rst deleted file mode 100644 index f27715d56..000000000 --- a/doc/gettingstarted-intro.rst +++ /dev/null @@ -1,35 +0,0 @@ -.. SPDX-License-Identifier: GPL-3.0-or-later - -.. _gettingstarted: - -Welcome to Knot Resolver's documentation for getting started! -This chapter will introduce Knot Resolver and will guide you through :ref:`installation ` to first :ref:`startup ` and basic insight into :ref:`configuration `. - - -.. _gettingstarted-intro: - -************ -Introduction -************ - -If you are an advanced user and want to use Knot Resolver like before version 6, you can switch to :ref:`usage without the manager `, for other users, it is recommended to stick to this chapter. - -================== -Basic architecture -================== - -The resolver is made up of several singlethread processes: - -:kresd: - The resolving daemon that is the core of the resolver, written in C. - Most of its functionalities are implemented in a separate modules written in C or Lua. - -:kres-cache-gc: - Garbage collector that takes care of maintaining the resolver's cache, written in C. - -:kres-manager: - A new process since version ``6.x`` that is used to manage other processes, written in Python. - The manager starts and setups other processes based on the configuration. - It is the only process that a user should directly interact with. - -For a detailed info see :ref:`internal architectire `.