On Fri, Jul 12, 2013 at 11:44 AM, Jonny Törnbom <[email protected]>wrote:
> On Fri, Jul 12, 2013 at 11:11:04AM +0200, Rainer Gerhards wrote: > > On Fri, Jul 12, 2013 at 11:03 AM, Jonny Törnbom <[email protected] > >wrote: > > I agree that it is really a problem outside of rsyslog, even if it > affects rsyslog (or any other logging solution for that matter). We are > bugging the "other mailing list" about the issue and will hopefully come > up with a solution. > > Now I know atleast that there isn't an easy workaround from rsyslog > side, but I will definitely let you know if what we come up with can > be of help to other rsyslog+systemd users. > > Well, technically the problem is that the issue already has happened before rsyslog is even started. So whatever we would try to do (e.g. increasing buffers) doesn't help, as it is too late at that point in time. So I don't see any solution except that the journal gets fixed. If I would see one, I'd definitely try to implement it, but again: whatever we do -- it's simply too late, damage already occured... Rainer > Thanks for your time. > > Regards, > Jonny > _______________________________________________ > 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. > _______________________________________________ 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.
