On Samstag, 13. Juli 2024 17:44:54 MESZ Andrei Borzenkov wrote:
On 13.07.2024 18:42, mh@mike.franken.de wrote:
On Samstag, 13. Juli 2024 17:35:33 MESZ Andrei Borzenkov wrote:
On 13.07.2024 18:16, mh@mike.franken.de wrote:
On Samstag, 13. Juli 2024 16:55:13 MESZ Andrei Borzenkov wrote:
On 13.07.2024 17:39, mh@mike.franken.de wrote:
On Samstag, 13. Juli 2024 16:25:16 MESZ Andrei Borzenkov wrote: [...]
If it would have been killed before, because of running into the dispatcher timeout, I'd suspect it would be running afterwards!?!?
^ not
I am sorry, I do not understand what you are saying. I suspect "not" is missing somewhere, just not sure where.
Missing "not" indeed.
OK, but again - we have no idea when script had been started, how long it has been running etc. We have really zero information and only have you conclusions that we cannot verify without facts.
As I wrote: My script only needs 1-2 seconds according to it's own log and according to the journal entries. What further facts can I provide?
You can explain the problem so that others also understand it. If you suspend your system 1 second after script has been started it will run 1 more second after resume. I still do not understand the problem.
Sry, I am not a native speaker, so sometimes it is not easy to find the correct wording. But: No, the system takes another about 50 seconds to finally enter sleep state. Even systemd scripts in /usr/lib/systemd/system-sleep/ are started and finished afterwards. And whats more: It worked for at least a few years without any problems. As I also wrote, the problems started with the before last NM version. My script didn't change in the last months. My conclusion: Something must have changed in NM.