Hi all,
It has been a while since I implemented the fw_log support. What I do
remember is, I modelled it in a similar fashion as Felix does. In there the
log_service is not used due to locking [1].
I don't remember the details, but with Celix for several calls this would
be a problem as well. If
Hello Bjoern,
Disclaimer: I did not look at the current codebase, but from your mail a assume
that the framework currently logs to some internal log component (that maybe
writes to stdout or a log file) and you are asking if it is a good idea to
redirect log information to the actual log servic
Good morning Gerrit,
that is also what I had in mind, but from looking at the code
(celix_log.c) , I don't see that the log_service will ever be used for
fw_log calls and was just wondering whether there is a reason for that?!
Regards,
Björn
On 09/10/2014 07:33 AM, Gerrit Binnenmars wr
Hello Bjorn,
The original idea was that fw_log was used when no log_service is available
(e.g. the fw_log() calls in the start-up and shutdown of the framework), as
soon as a log service is available it shall also be used for framework
logging. Don't know how it is actually implemented right now.
Hi everyone,
After replacing a bunch of printf's through fw_log calls and integrating
the log_writer_syslog bundle, I was wondering why the fw_log isn't
actually a serviceTracker to also use the log_service (when available).
Is there any reason for that? Wouldn't that make sense?
Regards,
