Our focus needs to be implementation. I was hoping the CEE was a bit closer to being finalized, but it seems like there is still some unanswered questions regarding the spec.
For lumberjack implementatons, we have the ceelog (rename?), libumberlog, rsyslog and syslogNG.
I agree with Rainer that we need to step carefully and probably want to view lumberjack as a fork of CEE, with the goal of feeding back issues to the CEE project and hopefully a merger of the two in the not too distant future.
On Tue, 2012-10-09 at 12:42 +0000, Rainer Gerhards wrote:
Hi all,
at least some of us seem to share a concern that CEE will depart from what it was early this year into a big monster effort that needs complete software overhaul. That would obviously be quite incompatible with what we are trying to do.
With the lumberjack-enabled software not yet rolled out widely, I think we have a final time to make a decision on the cookie. Currently we use "@cee" to detect lumberjack-enabled message content. With the potential fork of the efforts, I think it would probably be wiser to change that to something like "@lj:" (or similar).
This change would hurt rsyslog (and our Windows products) a little, but I get the impression that this may be a wise step in the long term.
Comments (especially from other implementers)?
Rainer _______________________________________________ lumberjack-developers mailing list lumberjack-developers@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/lumberjack-developers