Ansible timers should not run on USB stick

[Debilski]

Otherwise the stick changes while it is being copied. (Although the whole mechanism seems messy. Can we boot the USB stick in a read-only way?)
Either doinst enables the timers on the target manually or we add a ConditionPathExists and check for a file that doinst creates to enable it or something like a negated ConditionHost and we have to set the specific hostname of the machine.

[Debilski]

I disabled the timers in df88241 (and currently anything other than running the all.yml playbook will disable them again though this probably should be changed)

For now the timers or services must be manually started on the new image, after doinst has copied the image.

[otizonaizit]

how do we enable the timers manually? Can you post here the needed command?

[Debilski]

As they are in a preset, I think there are actually already activated?Am 24.08.2024 um 14:14 schrieb Tiziano Zito ***@***.***>: how do we enable the timers manually? Can you post here the needed command? —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>

[Debilski]

Otherwise it’s something like    ln -s $TARGET/usr/local/systemd/system/ansible-pull-init.timer $TARGET/etc/systemd/system/timers.target.wants/ansible-pull-init.timerPaths are guesses. I have very spotty network.Am 24.08.2024 um 15:57 schrieb Rike-Benjamin Schuppner ***@***.***>:As they are in a preset, I think there are actually already activated?Am 24.08.2024 um 14:14 schrieb Tiziano Zito ***@***.***>: how do we enable the timers manually? Can you post here the needed command? —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>