You can see a lot of messages that are doing the particulars of a deamon's event handling but are not in that daemon's log file
There seems to be a little randomness about this I've also heard that sometimes the eventd messages are in collectd's logs
Just trying to figure out how this worked before and what broke it.
Note I have already hacked the onEvent method for collectd to force setting the prefix.
Acceptance / Success Criteria
None
Attachments
1
Lucidchart Diagrams
Activity
Seth Leger May 1, 2012 at 5:52 PM
I've changed the code that uses java.util.concurrent ThreadPoolExecutors so that they use a ThreadFactory that will name the threads with nice names. This ThreadFactory can also be configured to force the ThreadPrefix of the caller on all created threads, which is just what needs to happen in Eventd. This way, if a class registers for events then all events that are received by that registration end up in the same log. Marking as fixed.
A large number of event handlers are logging to the eventd.log file rather than the log file belonging to the event handler.
to see this download the attached tgz and untar' it
then execute:
grep – '-Thread' eventd.log | grep -v EventIpcManagerDefaultImpl
You can see a lot of messages that are doing the particulars of a deamon's event handling but are not in that daemon's log file
There seems to be a little randomness about this I've also heard that sometimes the eventd messages are in collectd's logs
Just trying to figure out how this worked before and what broke it.
Note I have already hacked the onEvent method for collectd to force setting the prefix.