On 3/2/22 11:50, Lennart Poettering wrote:
On Mi, 02.03.22 12:29, Manuel Wagesreither (man...@fastmail.fm) wrote:
Hi all,
My embedded system is shutting down rather slow, and I'd like to find out the
responsible processes.
[ 7668.571133] systemd-shutdown[1]: Waiting for process: dockerd,
On Mi, 02.03.22 12:29, Manuel Wagesreither (man...@fastmail.fm) wrote:
> Hi all,
>
> My embedded system is shutting down rather slow, and I'd like to find out the
> responsible processes.
>
> [ 7668.571133] systemd-shutdown[1]: Waiting for process: dockerd, python3
> [ 7674.670684]
On Mi, 02.03.22 13:02, Arian van Putten (arian.vanput...@gmail.com) wrote:
> I've seen this a lot with docker/containerd. It seems as if for some reason
> systemd doesn't wait for their cgroups to cleaned up on shutdown. It's
> very easy to reproduce. Start a docker container and then power off
I've seen this a lot with docker/containerd. It seems as if for some reason
systemd doesn't wait for their cgroups to cleaned up on shutdown. It's
very easy to reproduce. Start a docker container and then power off the
machine. Since the move to cgroups V2 containerd should be using systemd to
>> I currently have no idea how to express this in systemd terms. If someone on
>
>> this list could provide some advice, it would be much appreciated.
>
> As for the recent "firmware flashing" thread I think it would be best to
> handle that via some boot parameter and something like a "boot
Hi all,
My embedded system is shutting down rather slow, and I'd like to find out the
responsible processes.
[ 7668.571133] systemd-shutdown[1]: Waiting for process: dockerd, python3
[ 7674.670684] systemd-shutdown[1]: Sending SIGKILL to remaining processes...
Is there a way for
