On Fri, 14.08.15 13:20, giulix (giulio.marti...@gmail.com) wrote:
> Hello,
>
> I have a process that reads from the journald log file. It gets a
> notification from inotify that something's changed, opens the journal, skims
> through it for messages it's interested in, does its stuff and closes t
Mantas,
I do not want to reimplement all the logic myself, I just want to get
journal entries directly at the source. The syscall you listed will do
nicely, thank you, provided it supplies the right inode everytime my
process is awakened by inotify. I will test it in the next hours/days.
Tha
On Fri, Aug 14, 2015 at 2:20 PM, giulix wrote:
> Hello,
>
> I have a process that reads from the journald log file. It gets a
> notification from inotify that something's changed, opens the journal,
> skims through it for messages it's interested in, does its stuff and closes
> the journal file (
Hello,
I have a process that reads from the journald log file. It gets a
notification from inotify that something's changed, opens the journal,
skims through it for messages it's interested in, does its stuff and
closes the journal file
(http://www.giulix.it/content/extracting-data-systemd-jo