From 560470b55207da4855c99d6a4829a43eb1f31f00 Mon Sep 17 00:00:00 2001 From: Wojciech Kozlowski Date: Tue, 9 Apr 2019 22:38:35 +0200 Subject: [PATCH] doc: replace old text with info about integrated configuration mode Signed-off-by: W. Kozlowski --- doc/user/overview.rst | 15 +++++++-------- 1 file changed, 7 insertions(+), 8 deletions(-) diff --git a/doc/user/overview.rst b/doc/user/overview.rst index e90b84b02b..6aa9462297 100644 --- a/doc/user/overview.rst +++ b/doc/user/overview.rst @@ -107,14 +107,13 @@ An illustration of the large scale architecture is given below. The multi-process architecture brings extensibility, modularity and -maintainability. At the same time it also brings many configuration files and -terminal interfaces. Each daemon has its own configuration file and terminal -interface. When you configure a static route, it must be done in the *Zebra* -configuration file. When you configure BGP network it must be done in the -*bgpd* configuration file. This can become difficult to manage. To resolve the -problem, FRR provides integrated user interface shell called *vtysh*. *vtysh* -connects to each daemon with UNIX domain socket and then works as a proxy for -user input. +maintainability. All of the FRR daemons can be managed through a single +integrated user interface shell called *vtysh*. *vtysh* connects to each +daemon through a UNIX domain socket and then works as a proxy for user input. +In addition to a unified frontend, *vtysh* also provides the ability to +configure all the daemons using a single configuration file through the +integrated configuration mode avoiding the problem of having to maintain a +separate configuration file for each daemon. Supported Platforms ===================