日本語のみで絞り込む
2022/11/3 -It seems to be a bug in systemd, it certainly shouldn't happen. There's not much information about it but from the bug description it looks like ...
If false, an elapsed timer unit that cannot elapse anymore is unloaded once its associated unit deactivated again. Turning this off is particularly useful ...
2019/9/16 -Persistent=false (i.e. default) keeps disabled the function to catch timers missed during system shutdown. In your case the system is on-line ...
2026/2/15 -Timers are systemd unit files whose name ends in .timer that control .service files or events. Timers can be used as an alternative to cron ...
2019/9/5 -I was also hoping that --timer-property=Persistent=false would achieve what I want... ... I can do a similar thing by creating an explicit timer ...
2024/10/10 -the Persistent option, which is mandatory in my casa since I use a laptop (so often turned off) is available only with OnCalendar timer option, ...
2025/7/31 -When I start the computer the next morning, it immediately shuts down after waking up. I thought Persistent=false would prevent that, but it ...
4日前 -Although timers are normally persistent, systemd also allows to set up transient timers that are only valid for the current session. Real ...
2020/6/9 -The issue is that it's supposed to run only at 4am but if I reboot it will try to run on startup. I've tried changing Persistent to false with ...
Systemd timers don't have a direct "persistent" option like cron's @reboot, but you can mimic it with Persistent=true in the timer unit.