diff options
| author | Quentin Young <qlyoung@users.noreply.github.com> | 2018-10-25 15:46:51 -0400 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2018-10-25 15:46:51 -0400 |
| commit | dd5c280ab3ae493e038ca13b672da148ade58f61 (patch) | |
| tree | 498f2d6f82500fb304e37771d21d48c6185d089f /doc/manpages/zebra.rst | |
| parent | 6cd85474f80492d4721966610357109593ae4ab9 (diff) | |
| parent | 0437e10517aa0b6c2e3490626333a0082ff4c79f (diff) | |
Merge pull request #3247 from opensourcerouting/spelchek
*: spelchek
Diffstat (limited to 'doc/manpages/zebra.rst')
| -rw-r--r-- | doc/manpages/zebra.rst | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/manpages/zebra.rst b/doc/manpages/zebra.rst index a8a9301588..cfb368bf44 100644 --- a/doc/manpages/zebra.rst +++ b/doc/manpages/zebra.rst @@ -33,7 +33,7 @@ OPTIONS available for the |DAEMON| command: Set netlink receive buffer size. There are cases where zebra daemon can't handle flood of netlink messages from kernel. If you ever see "recvmsg overrun" messages in zebra log, you are in trouble. - Solution is to increase receive buffer of netlink socket. Note that kernel < 2.6.14 doesn't allow to increase it over maximum value defined in /proc/sys/net/core/rmem_max. If you want to do it, you have to increase maximum before starting zebra. + Solution is to increase receive buffer of netlink socket. Note that kernel < 2.6.14 doesn't allow increasing it over maximum value defined in /proc/sys/net/core/rmem_max. If you want to do it, you have to increase maximum before starting zebra. Note that this affects Linux only. |