From c34b6b577ef58e7609de1e088e7923c4c056cfeb Mon Sep 17 00:00:00 2001 From: hasso Date: Tue, 31 Aug 2004 13:41:49 +0000 Subject: Commit my hack (yes, I still call it hack) - command line switch for zebra daemon to change netlink receive buffer size. --- doc/ChangeLog | 4 ++++ doc/zebra.8 | 12 ++++++++++++ 2 files changed, 16 insertions(+) (limited to 'doc') diff --git a/doc/ChangeLog b/doc/ChangeLog index 63b736cc..97dddece 100644 --- a/doc/ChangeLog +++ b/doc/ChangeLog @@ -1,3 +1,7 @@ +2004-08-31 Hasso Tepper + + * zebra.8: Document -s/--nl-bufsize command line switch. + 2004-08-27 Hasso Tepper * Update vtysh man page to reflect changes in shell. diff --git a/doc/zebra.8 b/doc/zebra.8 index 8f830152..25cbb363 100644 --- a/doc/zebra.8 +++ b/doc/zebra.8 @@ -71,6 +71,18 @@ name at the moment. Default is \fIquagga\fR. \fB\-r\fR, \fB\-\-retain\fR When the program terminates, retain routes added by \fBzebra\fR. .TP +\fB\-s\fR, \fB\-\-nl-bufsize \fR\fInetlink-buffer-size\fR +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 +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. + +Note that this affects Linux only. +.TP \fB\-v\fR, \fB\-\-version\fR Print the version and exit. .SH FILES -- cgit v1.2.1