> Starting this morning I have begun to wade in-depth through a pile of CEE > docs (the upcoming standard). We may need to make some format adjustments, > but I'd like to stick with somewhat as simple as possible to write for the > samples.
Do you have a link to the CEE documentation for the upcoming
standard? I'd be interested in taking a look.
> > Will the log formats, that is, what to look for,
> > be in a seperate text file that can be updated? As you mention in the
> > blog post, "much like a virus scanner".
>
> Actually, at this point nothing is really finalized. For the initial effort,
> it will definitely be a text file. But in the long term I can also envision
> that we should be able to pull it e.g. from web servers or load multiple
> files, or... actually something that should be configurable.
IMHO, I think leaving it a text file would be best. Let some
other process (wget, whatever) pull the definitions. Or let the user
do it manually. Again, IMHO, I think having the actual library pull
the definitions might be outside of the scope.
>
> > If that is the case, will programs that use liblognorm pull that into
> > an array first, and let liblognorm do it's work? Or will this file
> > have to be repeatedly referenced?
>
> In the long term I think it makes sense to provide a way to stuff samples in
> via either a dedicated API OR (and?) have them loaded based on a config file.
> The latter is what I have on my mind for the first step.
Sounds great.
> > I'd love to help out in this, be it code wise and/or log examples.
>
> Any help is deeply appreciated and these questions already help! Log samples
> and trying out the library, once it materializes, would be a very very great
> aid.
>
> I will write a couple of more blog posts with more details, and everything is
> really open for change now. It would also be very useful if you could spread
> the news. An as wide audience as possible would be very good.
Sounds great as well. I know on this end of the wire, you've
already got one beta tester :) I'm really itching to try it out, but I
know it's not even near that point! I'll be more than happy to help
out where I can (code, log examples, etc).
--
Champ Clark III | Softwink, Inc | 800-538-9357 x 101
http://www.softwink.com
GPG Key ID: 58A2A58F
Key fingerprint = 7734 2A1C 007D 581E BDF7 6AD5 0F1F 655F 58A2 A58F
If it wasn't for C, we'd be using BASI, PASAL and OBOL.
pgpVLWL5ofNOg.pgp
Description: PGP signature
_______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com
