Re: Syslog-sec-misc @ SF: syslog-sec: API, standards and 'host'BSD

[Martin S. <li...@ms...>]

Albert Mietus schrieb:
> Then, each *BSD can easily port the (our) SF code there BSD, by  
> taking the host/* version and the shared -sec code.

Ack.

>>>  API which is intended to replace syslog(3).
> Don't bed on that. I have seen several would be replacements for  
> syslog. They generaly fail to replace syslog, or the fail completely.
> 
> So stick to syslog and it standards. Sure learn from all. But focus  
> on syslog-sec!

Of course _any_ "replacement" will be just an additional function. 
syslog(3) is widely used and will stay for some decades.

But I would like my software to move forward to syslog-protocol with its 
additional data fields; one way to push that is by providing one new API 
that makes it easy to include IDs and structured data.
In that respect even Apple's asl is not really sufficient to be that new 
API, because
a) the new MSGID field is not supported (although this could be worked 
arround), and more important
b) the key=value pairs have predefined keys, and even if implemented 
with arbitrary keys there is no way to specify the namespace (=SD-ID).
So this API would not enable, but prevent a move to syslog-protocol. :-/

This whole API question is not really part of syslog-sec, but some work 
in this direction belongs to my GSoC project.

-- 
Martin