Hi,
On Sat, 14.06.2008 at 01:39:29 +0200, Claudio Jeker  wrote:

quoted text
> Nope. That is not the problem. The main issues is that a full view will

> need a lot of memory for the sysctl. This memory needs to be available as

> real memory because it is wired into the kernel. If you run bgpd with full

> views on a box with less then 512MB of RAM you're most probably run out of

> memory. Theo and I had a look at this and bailing out in this situation is

> the right thing to do.

thanks for the explanation!
> The right fix is to just spend 50 bucks on 1-2GB of additional RAM.
I'll look into finding appropriate RAM and/or putting that card into a

different box.
> c) work around (ugly but works)

quoted text
> netstat -rnfinet -M /dev/mem

Nice!
> d) the route sysctl needs to be rewritten to be fully restartable and so

quoted text
> small chunks of the table can be fetched one after the other. This is a

> massive change and it will not happen for the upcomming release.

I'm not sure that I understand the need to copy the table, or parts

thereof, correctly. Sure, the table changes all the time. So, the

routes viewed when running 'netstat -r' are only a snapshot and may have

changed by the time the user views them, anyway.
Would it be possible to walk along the live table, without copying the

table, or would the continuous stream of route inserts and deletes lead

to a corrupted view and/or access to the wrong parts of the system's

memory (which must to be prevented), or would this be such a

performance hit that this is unfeasible?
Kind regards,

--Toni++