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.
As a result, distros start it later by default.
And now that systemd is supposed to replace all logging, and the systemd people
advocate that they should not push logs to rsyslog, but should instead write
them to disk for rsyslog to poll for later, their viewpoint is that it doesn't
matter how late rsyslog is started (they prefer not having rsyslog running,
systemd should solve all logging problems, including inventing a new network
protocol)
if systemd will loose logs before rsyslog starts, and systemd insists on being
the thing to start rsyslog. I view this as a systemd bug (and will work to
configure my machines sanely, in spite of systemd.
but in any case, the rsyslog project has very little influence on when the
distros configure systemd to start rsyslog :-(
I know this isn't a good answer, but hopefully it helps explain why we don't
have a good answer.
David Lang
_______________________________________________
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.
