Hi Mantas,
thank you for your helpful input. My main error was probably that I was accidentially using "TimeoutStartSec" instead of "TimeoutStopSec". My current implementation now looks like this:
[Unit]
Description=Wait for backups
After=ssh.service remote-fs.target rsyslog.service
Requir
Would the systemd inhibit interface be an option?
https://www.freedesktop.org/wiki/Software/systemd/inhibit/
It was designed for that use case after all.
Am Mo., 29. Aug. 2022 um 14:01 Uhr schrieb Mantas Mikulėnas :
>
> On Mon, Aug 29, 2022 at 1:31 PM Henning Moll wrote:
>>
>> Hi,
>>
>> back in
>>> Toomas Rosin schrieb am 26.08.2022 um 19:22 in Nachricht
<6751.1661534553@toomas>:
> Hi,
>
> Arseny Maslennikov wrote:
>
>> $ TTYID=tty2 # for example
>> $ ln ‑s /dev/null /etc/systemd/system/autovt@$TTYID.service
>
> This works, thank you!
Would the command above be the same as "systemct
Hi,
This is an interesting mechanism, but unfortunately it is to weak for my use case: It does only delay reboots which are initiated via "systemctl ...". A "sudo reboot" is not delayed
Best regards
Henning
Gesendet: Dienstag, 30. August 2022 um 10:14 Uhr
Von: "Michael Biebl"
An: "M
I'm currently running systemd 219-78.
I realize there's significant behavior differences in the current release, but
per the documentation, I take it the behavior of '-clean' hasn't changed in
regards to directly specifications only applying to the directory entry and the
top level files. AKA,
>>> Henning Moll schrieb am 30.08.2022 um 16:24 in
Nachricht
:
> Hi,
>
> This is an interesting mechanism, but unfortunately it is to weak for my use
> case: It does only delay reboots which are initiated via "systemctl ...". A
> "sudo reboot" is not delayed
At least in the past there was a di
>>> SCOTT FIELDS schrieb am 30.08.2022 um 21:15 in
Nachricht
> I'm currently running systemd 219‑78.
>
> I realize there's significant behavior differences in the current release,
> but per the documentation, I take it the behavior of '‑clean' hasn't changed
> in regards to directly specifica
Just tried "shutdown -r now" and unfortunately it also doesn't care about systemd-inhibit.
Gesendet: Mittwoch, 31. August 2022 um 08:07 Uhr
Von: "Ulrich Windl"
An: "Michael Biebl" , newssc...@gmx.de
Cc: "systemd-devel@lists.freedesktop.org"
Betreff: Antw: [EXT] Re: [systemd-devel] Help requ
>>> Henning Moll schrieb am 31.08.2022 um 08:13 in
Nachricht
:
> Just tried "shutdown -r now" and unfortunately it also doesn't care about
> systemd-inhibit.
Is the systemd shutdown target triggered anyway? I guess it is. If so, the
problem must be deeper "under the hood".
> Gesendet: Mittwoch,
