Hello,
I began to explore the new OCL component for real-time logging (log4cpp). As
stated by the documentation [1], the current _official_ implementation is
only available through the OCL component. It is stated that an RTT branch
exists to make the RTT::Logger uses the new log4cpp. Is there any actual
plan to merge this in the master RTT branch? We are very interested in this
new feature, but one major drawback is that we now have two different logs.
Also, is there any plan to make a CORBA appender, i.e. having many
CORBAAppender with a single FileAppender?
Best regards,
Philippe
[1]
http://www.orocos.org/wiki/rtt/rtt-20/real-time-logging/using-real-time-...
Log4cpp implementation of RTT::Logger and centralized/networked
On Jan 11, 2011, at 09:07 , Philippe Hamelin wrote:
> Hello,
>
> I began to explore the new OCL component for real-time logging (log4cpp). As stated by the documentation [1], the current _official_ implementation is only available through the OCL component. It is stated that an RTT branch exists to make the RTT::Logger uses the new log4cpp. Is there any actual plan to merge this in the master RTT branch? We are very interested in this new feature, but one major drawback is that we now have two different logs.
I've had the RTT::Logger-using-log4cpp working for months now, but it still has some serious wrinkles. I would be hesitant to put this out to the general public. The idea is good, but there are definitely usability issues.
> Also, is there any plan to make a CORBA appender, i.e. having many CORBAAppender with a single FileAppender?
The current limitation is that each category has only one output buffer port. So you can really only attach one appender to the other end of the port. This was simply the easiest way to get it to work - it is not an limitation of log4cpp itself (which does allow multiple appenders per category). We could modify the implementation to support multiple ports (and hence appenders) per category (probably the best long-term plan), or you could try things out by writing a multiplexing appender component that has one category's port as an input, and then that appender outputs to multiple other appenders.
HTH
S