proxmox-mirrors/mirror_frr
1
0
Fork 0
mirror of https://git.proxmox.com/git/mirror_frr synced 2025-08-15 20:32:18 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

doc: strip trailing whitespace

Browse Source 
Signed-off-by: Quentin Young <qlyoung@cumulusnetworks.com>
This commit is contained in:
Quentin Young 2018-10-28 01:07:06 +00:00
parent a353782e3b
commit 4c97fd1a87
7 changed files with 13 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
doc/developer/building-frr-for-ubuntu1804.rst
View File

@ -115,7 +115,7 @@ Create empty FRR configuration files
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Although not strictly necessary, it's good practice to create empty Although not strictly necessary, it's good practice to create empty
configuration files _before_ starting FRR. This assures that the permissions configuration files _before_ starting FRR. This assures that the permissions
are correct. If the files are not already present, FRR will create them. are correct. If the files are not already present, FRR will create them.
It's also important to consider _which_ files to create. FRR supports writing It's also important to consider _which_ files to create. FRR supports writing

6
doc/developer/modules.rst
View File

@ -103,9 +103,9 @@ standard entry point for loadable modules.
Command line parameters Command line parameters
----------------------- -----------------------
Command line parameters can be passed directly to a module by appending a Command line parameters can be passed directly to a module by appending a
colon to the module name when loading it, e.g. ``-M mymodule:myparameter``. colon to the module name when loading it, e.g. ``-M mymodule:myparameter``.
The text after the colon will be accessible in the module's code through The text after the colon will be accessible in the module's code through
``THIS_MODULE->load_args``. For example, see how the format parameter is ``THIS_MODULE->load_args``. For example, see how the format parameter is
configured in the ``zfpm_init()`` function inside ``zebra_fpm.c``. configured in the ``zfpm_init()`` function inside ``zebra_fpm.c``.

2
doc/developer/next-hop-tracking.rst
View File

@ -269,7 +269,7 @@ RNH table::
O O O O
/ \ / \
O O O O
struct rnh struct rnh
{ {
uint8_t flags; uint8_t flags;

4
doc/developer/process-architecture.rst
View File

@ -118,7 +118,7 @@ The following diagram illustrates a simplified version of this infrastructure.
.. todo: replace these with SVG .. todo: replace these with SVG
.. figure:: ../figures/threadmaster-single.png .. figure:: ../figures/threadmaster-single.png
:align: center :align: center
Lifecycle of a program using a single threadmaster. Lifecycle of a program using a single threadmaster.
The series of "task" boxes represents the current ready task queue. The various The series of "task" boxes represents the current ready task queue. The various
@ -183,7 +183,7 @@ running their own ``threadmaster``-based event loop.
.. todo: replace these with SVG .. todo: replace these with SVG
.. figure:: ../figures/threadmaster-multiple.png .. figure:: ../figures/threadmaster-multiple.png
:align: center :align: center
Lifecycle of a program using multiple pthreads, each running their own Lifecycle of a program using multiple pthreads, each running their own
``threadmaster`` ``threadmaster``

4
doc/user/installation.rst
View File

@ -385,7 +385,7 @@ Additional kernel modules are also needed to support MPLS forwarding.
appropriate value. appropriate value.
:makevar:`VRF forwarding` :makevar:`VRF forwarding`
General information on Linux VRF support can be found in General information on Linux VRF support can be found in
https://www.kernel.org/doc/Documentation/networking/vrf.txt. Kernel https://www.kernel.org/doc/Documentation/networking/vrf.txt. Kernel
support for VRFs was introduced in 4.3 and improved upon through support for VRFs was introduced in 4.3 and improved upon through
4.13, which is the version most used in FRR testing (as of June 4.13, which is the version most used in FRR testing (as of June
@ -421,7 +421,7 @@ Additional kernel modules are also needed to support MPLS forwarding.
included in future kernel versions so upgrading your kernel may also included in future kernel versions so upgrading your kernel may also
address this issue. address this issue.
Building Building
^^^^^^^^ ^^^^^^^^

6
doc/user/static.rst
View File

@ -9,7 +9,7 @@ of static routes.
.. _starting-static: .. _starting-static:
Starting STATIC Starting STATIC
=============== ===============
Default configuration file for *staticd* is :file:`staticd.conf`. The typical Default configuration file for *staticd* is :file:`staticd.conf`. The typical
@ -45,11 +45,11 @@ a static prefix and gateway.
initial form of the command. GATEWAY is gateway for the prefix it currently initial form of the command. GATEWAY is gateway for the prefix it currently
must match the v4 or v6 route type specified at the start of the command. must match the v4 or v6 route type specified at the start of the command.
GATEWAY can also be treated as an interface name. If the interface name GATEWAY can also be treated as an interface name. If the interface name
is ``null0`` then zebra installs a blackhole route. TABLENO is ``null0`` then zebra installs a blackhole route. TABLENO
is an optional parameter for namespaces that allows you to create the is an optional parameter for namespaces that allows you to create the
route in a specified table associated with the vrf namespace. table will route in a specified table associated with the vrf namespace. table will
be rejected if you are not using namespace based vrfs. ``nexthop-vrf`` be rejected if you are not using namespace based vrfs. ``nexthop-vrf``
allows you to create a leaked route with a nexthop in the specified VRFNAME allows you to create a leaked route with a nexthop in the specified VRFNAME
vrf VRFNAME allows you to create the route in a specified vrf. vrf VRFNAME allows you to create the route in a specified vrf.
``nexthop-vrf`` cannot be currently used with namespace based vrfs ``nexthop-vrf`` cannot be currently used with namespace based vrfs
currently as well. currently as well.

2
doc/user/zebra.rst
View File

@ -186,7 +186,7 @@ Standard Commands
Enable/disable link-detect on platforms which support this. Currently only Enable/disable link-detect on platforms which support this. Currently only
Linux and Solaris, and only where network interface drivers support Linux and Solaris, and only where network interface drivers support
reporting link-state via the ``IFF_RUNNING`` flag. reporting link-state via the ``IFF_RUNNING`` flag.
In FRR, link-detect is on by default. In FRR, link-detect is on by default.
.. _link-parameters-commands: .. _link-parameters-commands: