On Sat, Apr 7, 2018, at 13:17, Christof Schulze wrote: > Hello > > When looking at the output of the monitor command, I saw those lines > following each other within a very short time: > > change neighbour 560221ea6f60 address fe80::183b:50ff:fe6e:f7df if > babel-vpn-1374 reach ffff ureach 0000 rxcost 96 txcost 96 cost 96 > change neighbour 560221ea6f60 address fe80::183b:50ff:fe6e:f7df if > babel-vpn-1374 reach ffff ureach 0000 rxcost 96 txcost 96 cost 96 > > In general, the monitor command seems to create more data than I > expected. In this example, I cannot spot a change. > Why is this output generated and is it really necessary?
When I asked a long time ago for babelweb 1, the answer was that monitoring is stateless, and it's more reliable to keep it simple and verbose than to try and deduplicate, which could be buggy, would make the code more complex, etc. The idea is that whenever something might have changed, it is logged conservatively. I assume this argument still holds. -- Gabriel _______________________________________________ Babel-users mailing list Babel-users@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/babel-users
