diff options
| author | Ulrich Weber <ulrich.weber@Sophos.com> | 2013-01-22 10:39:18 +0000 |
|---|---|---|
| committer | David Lamparter <equinox@opensourcerouting.org> | 2013-02-23 18:19:24 +0100 |
| commit | f1ef81b2476ea533ac3d2129aa0e89653c427323 (patch) | |
| tree | 107bc07162b377b16af43d59cca4ce1a82a747f0 /doc | |
| parent | 66b63aa036c75737c3a8cea9693eff4dec84f903 (diff) | |
zebra: use SO_RCVBUFFORCE for netlink socket
so net.core.rmem_max must not be adjusted. Requires
linux kernel >= 2.6.14, falls back to SO_RCVBUF on error
Signed-off-by: Ulrich Weber <ulrich.weber@sophos.com>
Signed-off-by: David Lamparter <equinox@opensourcerouting.org>
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/zebra.8 | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/zebra.8 b/doc/zebra.8 index 23703e72..a40909a6 100644 --- a/doc/zebra.8 +++ b/doc/zebra.8 @@ -80,7 +80,7 @@ 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 -doesn't allow to increase it over maximum value defined in +< 2.6.14 doesn't allow to increase it over maximum value defined in \fI/proc/sys/net/core/rmem_max\fR. If you want to do it, you have to increase maximum before starting zebra. |