On Sat, Apr 2, 2016 at 1:59 PM, Michael Biebl <[email protected]> wrote: > 2016-04-02 9:14 GMT+02:00 Francis Moreau <[email protected]>: >> On Fri, Apr 1, 2016 at 10:50 PM, David Lang <[email protected]> wrote: >>> On Fri, 1 Apr 2016, fmoreau wrote: >>> >>>> Hi, >>>> >>>> This question was already asked in the past, see: >>>> http://permalink.gmane.org/gmane.comp.sysutils.rsyslog/9864 >>>> >>>> But IMHO the answers given weren't satisfactory. So I'm asking again. >>>> >>>> If there's no reason and rsyslog only needs the local fs to be settled >>>> then >>>> it should be started earlier to avoid missing some early messages sent by >>>> systemd. >>> >>> >>> The trouble is that it depends a lot on exactly what you have rsyslog >>> configured to do. Since rsyslog can send logs over the network, to >>> databases, etc, there are potentially a lot of thigns that need to be >>> started first. >> >> But shouldn't rsyslog be prepared to handle these cases where network >> isn't yet ready and should start sending logs over the network as soon >> as the network becomes available for example ? > > network is just one. logging to databases another. Those typically > have complexer requirements and aren't started in early boot.
and chances are that these requirements (by default) arent started before rsyslog is even if rsyslog is started after basic.target. Network for example by default is probably started and up long time after rsyslog is started by default. 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. Thanks. -- Francis _______________________________________________ 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.
