Greetings!
I noticed some strange behavior in dpkg with the latest update.
During deployment, I received the following warnings:
dpkg: warning: unable to delete old directory '/lib/systemd/system': Directory not empty
dpkg: warning: unable to delete old directory '/lib/systemd': Directory not empty
It's strange that dpkg is trying to delete these directories—they're system directories and are still occupied.
Here's what dpkg -S /lib/systemd/system/ returns: ksm-control-daemon: /lib/systemd/system
dpkg -S /lib/systemd/: ksm-control-daemon: /lib/systemd/system.
Is this normal behavior?
On nodes where I didn't have time to deploy the update,
dpkg -S /lib/systemd/ returns: ifupdown2, ksm-control-daemon: /lib/systemd/system
The ifupdown2 package is one of those that was updated.
I noticed some strange behavior in dpkg with the latest update.
During deployment, I received the following warnings:
dpkg: warning: unable to delete old directory '/lib/systemd/system': Directory not empty
dpkg: warning: unable to delete old directory '/lib/systemd': Directory not empty
It's strange that dpkg is trying to delete these directories—they're system directories and are still occupied.
Here's what dpkg -S /lib/systemd/system/ returns: ksm-control-daemon: /lib/systemd/system
dpkg -S /lib/systemd/: ksm-control-daemon: /lib/systemd/system.
Is this normal behavior?
On nodes where I didn't have time to deploy the update,
dpkg -S /lib/systemd/ returns: ifupdown2, ksm-control-daemon: /lib/systemd/system
The ifupdown2 package is one of those that was updated.