I understand it is not desirable to have duplicate logging, but there is
a corner case where logging that is done during systemd shutdown is lost
because rsyslog is killed. This makes shutdown look broken due to it
being non-deterministic exactly when rsyslog is killed.
Currently, the easiest way
I have been doing Xenial -> Bionic -> Focal release upgrades and started
running into this apparmor issue with dhclient after reaching Focal.
I don't know the root issue, and it doesn't appear to impact
functionality (at least as far as I can tell on my hosts). However, I am
currently dealing
Hi John,
Thank you for your detailed response and education on command text. I
was able to use pstree to see the thread command text behavior change
before and after the AppArmor rule addition. I feel better now that I
understand what is going on!
--
You received this bug notification because
I ran into this on an Xenial to Bionic upgrade. After the upgrade to
Bionic was complete, freshclam started trying to download clamav
database through my apt proxy. The database download attempts failed due
to apt proxy being strictly for apt only.
>From quick debugging... I think it might be