Yes, it is very easy.But I think that I will only be able to see in a few days whether the old behavior will return.Please be patient.
On Tue, 18 May 2021 18:18:37 +0200 Michael Biebl <bi...@debian.org> wrote: > Am 18.05.21 um 17:05 schrieb Michael Biebl: > > Am 18.05.21 um 16:37 schrieb UN-pi: > >> "systemctl status rsyslog.service" say: > >> > >> rsyslog.service - System Logging Service > >> Loaded: loaded (/lib/systemd/system/rsyslog.service; enabled; vendor > >> preset: enabled) > >> Active: active (running) since Wed 2021-05-12 17:27:41 CEST;5 days > >> ago > >> Docs: man:rsyslogd(8) > >> https://www.rsyslog.com/doc/ > >> Main PID: 302 (rsyslogd) > >> Tasks: 4 (limit: 1968) > >> CGroup: /system.slice/rsyslog.service > >> └─302 /usr/sbin/rsyslogd -n -iNONE > >> > > > > Ok, so you have single process. I don't see how --kill-who=main is going > > to make a difference here. > > > > Could you switch back to the original version without "--kill-who=main" > > and verify that this reintroduces the problem for you? >
