Hi!

...

There's a problem in the rip_tx_err fonction in proto/rip/rip.c. The proto name was badly set.

Here's a patch fixing it.

here's a patch to the patch forget a debug thing. Seriously please apply this one and not the other.

Patch looks good.

But it does not solve a real problem : If you've got a problem on interface (netfilter DROP by example). You've got the messages : bird: MyRIP: Unexpected error at rip transmit: Operation not permitted bird: MyRIP: Unexpected error at rip transmit: Operation not permitted bird: MyRIP: Unexpected error at rip transmit: Operation not permitted

till your disk is full (for embedded routers).

What can be done to avoid this ?

Not misconfigure your router, maybe? You might want to ratelimit somehow... Pavel -- Horseback riding is like software... ...vgf orggre jura vgf serr.

Hello!

that's it. If you have no suggestion I start code one. Is a modification of log() function a good idea ?

Yes, basically you can do the same as Linux syslogd does: remember the last message and if log() gets called another time for the same message, just count the occurences and when a different message arrives or some time passes, something like "Last message repeated NNN times" should be printed. A patch will be welcome. Have a nice fortnight -- Martin `MJ' Mares <mj@ucw.cz> http://atrey.karlin.mff.cuni.cz/~mj/ Faculty of Math and Physics, Charles University, Prague, Czech Rep., Earth A mathematician is a machine for converting coffee into theorems.