On Di, 16.06.20 11:22, darkpenguin (darkpeng...@yandex.com) wrote:
> I would be able to figure it out if systemd told me what is going on.
> This is my main point - maybe it should tell us immediately that "this
> process is stalling the shutdown" or "this thing reloads me too much"?
> And
On Mi, 13.05.20 08:34, darkpenguin (darkpeng...@yandex.com) wrote:
> I had trouble trying to paste a 70M text file to fpaste.org; here is the
> gzipped log of the shutdown process instead ('zcat journal.gz | less'
> works where other ways don't).
>
> >> Instead of 90 seconds of "Waiting for
On Di, 12.05.20 11:09, darkpenguin (darkpeng...@yandex.com) wrote:
> > Current versions (since ~231 iirc) of systemd log about the processes
> > they kill due to timeouts. You should find that in the logs.
>
> Package: systemd
> Version: 241-7~deb10u3
>
> I wanted to make sure I'm not missing
On So, 26.04.20 19:08, Dark Penguin (darkpeng...@yandex.com) wrote:
> Very often I have encountered one problem: during shutdown, systemd has
> to wait for something. Of course, it is probably different things every
> time, and it is probably not systemd's fault, at least some of the cases.
>
>
Very often I have encountered one problem: during shutdown, systemd has
to wait for something. Of course, it is probably different things every
time, and it is probably not systemd's fault, at least some of the cases.
This leads to the question: how do we find out the root of the problem?
Systemd
