Hi, Francis Moreau wrote: > So I don't really see why it's an issue to start rsyslog earlier since > it must already handle the case where those requirements are not ready > to work.
Don't forget setups where people specify IP addresses rsyslog should bind to. These interfaces must be ready to use *before* rsyslog tries to start. What's your problem in detail? You shouldn't really lose messages on start (you maybe have to increase your system's kernel buffer to catch an edge case). Like Michael wrote distributions have to choose a default which will work for *most* setups. Don't forget that you can easily overwrite units in systemd. If logging is really that critical for you, you definitely *should* customize buffers and boot order to match your requirement like you have already adjusted rsyslog's configuration to guarantee reliable logging. -Thomas _______________________________________________ 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.
