[systemd-devel] Linux Journal API/client lib
Rainer Gerhards
rgerhards at gmail.com
Sat Dec 3 08:36:36 PST 2011
On Sat, Dec 3, 2011 at 5:18 PM, Kay Sievers <kay.sievers at vrfy.org> wrote:
> You can just add a tiny bridge or make rsyslog receive the proper data
> which has no fixed wire format at all, but is an API we can extend as
> needed.
>
> Honestly, I really don't understand your claims, all will be available
> to you with just a few lines of code. Syslog should start integrating
> with the system...
Frankly, that's why I am asking in the first place. But it is
unavoidable to clarify some things while doing so.
One more question on the integration part. We now know that rsyslog
needs to read the journal and convert that into proper syslog format.
Given my experience with the Windows Event Log, I know that I need
some handle to tell the system "please give me everything from
checkpoint x and above". In Windows, I have unique keys for such
checkpoints, so that I know exactly to query from where. Is it your
intention to provide such a handle as well (I know I could check the
code, but that would give me just the current state and not what your
intention towards that thing is). It is important that the handle is
consistent and valid across reboot sessions. I guess you could use the
hash? Maybe that's the way things will work?
Rainer
More information about the systemd-devel
mailing list