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,
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:
>>> 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
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
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
