Hi, On Wed, Jul 10, 2013 at 06:20:59AM +0200, Michael Biebl wrote: > You can only start logging, once you have a write /var. >
Now I happen to have /var as logging directory and of course /var needs to be mounted for it to work. However that is not a problem since local filesystem is mounted before sysinit.target is reached. Shouldn't rsyslog be able to start after sockets.target but before basic.target and therefor be ready earlier and lose less messages? See this doc for systemd bootup: http://www.freedesktop.org/software/systemd/man/bootup.html Br, Jonny > 2013/7/9 Jonny Törnbom <[email protected]>: > > Hi, > > > > Is there a reason to why rsyslog starts after basic.target on > > systemd and not earlier? This is a bit related to the other > > issue about missing early boot-up messages due to journal socket > > getting full (only 11 messages can fit socket buffer) until messages > > starts to get dropped, until rsyslog starts later on. > > > > I'm quoting parts of an email from Umut Tezduyar from systemd mailing > > list: > > > > "Number of messages that can be queued on /run/systemd/journal/syslog > > is controlled by /proc/sys/net/unix/max_dgram_qlen and this value is > > by default 10 in most distributions. What this means is, after journal > > forwards 11 messages to the socket, it will not be able to do so until > > external logging daemon comes up and clears up > > /run/systemd/journal/syslog. If logging daemon is starting after > > basic.target, it is pretty certain that it will not be able to receive > > all the early boot messages." > > > > Thanks > > > > -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.
