[Babel-users] [PATCH] Allow to independently monitor events for neighbour, interface, route, xroute

[Christof Schulze]

>
>Groovy.
>
>> should not be able to stall it. The fix for this is rather involved as
>> it means we need to be able to decide which socket to close.
>
>Yes, I worried about long term connections stalling out babel.
>
>Fixing that:
>
>* Threaded I/O is no fun in C.
>* Flinging this info out into another, forked, non-blocking monitoring process is feasible
>
>Personally, I prefer an entirely separate box acting as a passive
>collector thing and to not be collecting such details at a router that
>needs to be routing...
It depends - in this case this is not so much about stats but about 
learning the proper babel neighbours in order to allow for multicast 
forwarding. So it is a features that has to exist on every node.

-- 
()  ascii ribbon campaign - against html e-mail
/\  against proprietary attachments

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/babel-users/attachments/20181129/db6356ac/attachment.sig>