On Thu, 30 Jan 2014, Igor Sverkos wrote:
...and if you really think you need to do something against systemd,
check if it possible to offer a rsyslog reader (a counterpart to
journalctl). It should be aware of every log target, should be able to
filter the data and so on. That's something the systemd folk is
showing to the user on every presentation...
rsyslog already includes this.
and we've already run into problems due to the binary journal files getting
corrupted and causing rsyslog to fill people's disks because the journal had a
backwards pointer in it.
David Lang
_______________________________________________
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.
