On 04/02/2016 09:14 AM, Francis Moreau wrote:
On Fri, Apr 1, 2016 at 10:50 PM, David Lang <[email protected]> wrote:
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 ?
That's probably already the case otherwise rsyslog won't be able to
handle gracefully any network disconnections or such.
Even with the default configuration, there are certain settings that are
initialized only during startup and which could depend on the network
being up - like host names, (AFAIR, rsyslog doesn't requery its local
host name after startup.) or UIDs obtained over network. There are
fallbacks, but these can cause issues even without anybody touching
rsyslog's configuration.
To get back to your original question...
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.
You're practically guaranteed to "loose" some late messages during
shutdown. This is not an issue as, if journald stores message on disk
and you're reading them via its API, you'll get them after next boot.
The point is that rsyslog can never start soon enough. The messages need
to be read asynchronously.
Tomas
_______________________________________________
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.
