On 07/10/2013 12:37 PM, Michael Biebl wrote:
2013/7/10 Jonny Törnbom<[email protected]>:
Hi,
Thanks for the reply. Though after I wrote my mail I switched my brain
on and realized that we don't actually store anything from journal. We
only use forwarding to socket, and then I guess the imjournal approach
doesn't work.
systemd still stores the messages, not on disk, but only in memory (on
the tmpfs in /run/log/journal) until the limits are reached defined in
journald.conf [1] and which can be tweaked via
RuntimeMaxUse=, RuntimeKeepFree=, RuntimeMaxFileSize=
That said, I dunno if imjournal needs a persistent journal file to
work properly. I guess you'd have to try.
I can confirm that the imjournal plugin needs a persistent or volatile
storage. It saves a cursor that is used to seek to the last position in
the journal - whether the original journal still exists or not - but is
has to have a journal file to read from. From the
sd_journal_get_cursor(3) man page:
Seeking to a cursor position without the specific entry being available
locally will seek to the next closest (in terms of time) available entry.
Tomas
Michael
[1] http://www.freedesktop.org/software/systemd/man/journald.conf.html
_______________________________________________
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com/professional-services/
What's up with rsyslog? Follow https://twitter.com/rgerhards
NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of
sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE
THAT.
