问题原文
原帖链接 · uli42 · CC BY-SA 4.0
We have multiple systems that suffer from a firmware bug. The vendor is aware of the problem and will fix the firmware bug. Until then we have to live with a workaround: restart the relevant service some time after bootup.
There are mechanisms in systemd to control the restart of a failed service but they are not of help here because the service starts successfully. Just delaying the start of the service by - say - 1 minute does not help, it needs to be started twice.
So what's the best way to automatically restart a service after the system is up?
社区高分解答
原帖链接 · John Mahowald · CC BY-SA 4.0
Create a .timer unit to control the .service unit.
Use the same base name as the service, so if the service were called thing, in /etc/systemd/system/foo.timer
[Unit]
Description=Start broken thing twice
[Timer]
OnBootSec=1min
OnBootSec=2min
[Install]
WantedBy=timers.target
Then enable this new timer. systemctl enable thing.timer
As the service remains active even if it has this problem, edit overrides such that it doesn't. systemctl edit thing.service
Which to change is hard to say without seeing the original unit. Perhaps add a ExecStartPost= command that returns 0 only if the device is in a good state. Or change RemainAfterExit=no to force a oneshot to not stay active.
摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。
