On Fri, Jul 12, 2013 at 12:22 PM, Tomas Heinrich <[email protected]>wrote:
> Hi, I'll try to summarize what was already said: > > - in this particular scenario, there is little that can be done on > rsyslog's side > > - the fact that imuxsock gets messages through journald limits its ability > to do any rate limiting / flow control > > - rsyslog can get all the messages that journald has through the imjournal > plugin > > The behavior of imuxsock has changed in that previously the services > calling syslog() blocked on the call until the message was written to the > socket. journald, as it seems, tries to write the message and discards it > if it fails. I'd say this is a regression that needs to be addressed. > journald should provide some means of flow control where one specifies > whether messages should be dropped at all or how large a backlog it should > keep. This will use up some memory but only for bursts. > I have used the weekend to check the facts and I think I agree. HTH Rainer _______________________________________________ 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.
