rsyslog.early.conf vs rsyslog.conf

Hi,

In 12.1 rsyslog uses rsyslog.early.conf in order to start early in the boot process. So how can I configure it for logging that requires services like network etc…? I am assuming I should configure rsyslog.conf, especially rsyslog.d dir for various additional modules I use, and then somehow force rsyslog restart with new config file after boot?

Or, because it’s a systemd service, it is safe to include all the config requiring network etc… via rsyslog.early.conf?

Any ideas?

Thanks!

On 2012-01-16 14:36, CanOfWires wrote:

> Or, because it’s a systemd service, it is safe to include all the
> config requiring network etc… via rsyslog.early.conf?

I don’t think you can log via network at the early stage, you have to wait
till the full service start, configured normally.


Cheers / Saludos,

Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)

Yes, and that’s why I ask. rsyslog uses /etc/rsyslog.early.conf because it starts early, before all services (like network) are available. So what do I need to do to enable full rsyslog logging? Restart rsyslog with DIFFERENT config (e.g /etc/rsyslog.conf configured for network logging etc…) after the boot is complete? If so, what must I configure to make it happen automatically?

There’s a bug report on this: Bug 728565
There are some useful workarounds in the bug report.

Excellent, thanks!