Hello,

I'm trying to get a better idea about how my stuff performs, and are
now looking for ideas on where any changes on art(4) interfaces are
recorded. Can we please have some general "play loud" option that would
send everything to syslog using eg. kern.info? Seeing malloc() failures
is probably a good thing, but a better thing is seeing a line flap if
it does, possibly with a differentiation between local and remote end.
Offhand, I don't see anything to this effect in the code (CVS), but
that may well be me.

Thank you!


Best,
--Toni++

Reply via email to