From owner-freebsd-net@FreeBSD.ORG  Fri Dec 26 09:31:13 2008
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
Delivered-To: net@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 1CF51106564A
	for <net@freebsd.org>; Fri, 26 Dec 2008 09:31:13 +0000 (UTC)
	(envelope-from eugen@kuzbass.ru)
Received: from www.svzserv.kemerovo.su (www.svzserv.kemerovo.su
	[213.184.65.80])
	by mx1.freebsd.org (Postfix) with ESMTP id 24FC18FC20
	for <net@freebsd.org>; Fri, 26 Dec 2008 09:31:04 +0000 (UTC)
	(envelope-from eugen@kuzbass.ru)
Received: from kuzbass.ru (kost [213.184.65.82])
	by www.svzserv.kemerovo.su (8.13.8/8.13.8) with ESMTP id mBQ9UvGd060409;
	Fri, 26 Dec 2008 16:30:58 +0700 (KRAT)
	(envelope-from eugen@kuzbass.ru)
Message-ID: <4954A459.37E85537@kuzbass.ru>
Date: Fri, 26 Dec 2008 16:31:05 +0700
From: Eugene Grosbein <eugen@kuzbass.ru>
Organization: SVZServ
X-Mailer: Mozilla 4.8 [en] (Windows NT 5.0; U)
X-Accept-Language: ru,en
MIME-Version: 1.0
To: Petri Helenius <petri@helenius.fi>
References: <20081225193818.GA9210@svzserv.kemerovo.su>
	<4953E89B.1060102@dlr.de>
	<DE2D92F5-A8ED-4988-BEA5-7CAB56FEFE02@helenius.fi>
Content-Type: text/plain; charset=koi8-r
Content-Transfer-Encoding: 7bit
Cc: Hartmut Brandt <hartmut.brandt@dlr.de>, net@freebsd.org
Subject: Re: bsnmpd & BGP full view
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Dec 2008 09:31:13 -0000

Petri Helenius wrote:

> > In any case it should re-read the kernel table only every 10 minutes
> > and in the mean time monitor the routing socket to update its copy
> > of the table. If of course someone is doing a lot of updates on
> 
> Why does it have to re-read the table periodically if it gets the
> updates anyway?

To protect from bugs that may lead to missed updates on rtsocket, I guess.