Timeline for Is there a way to know when a systemd timer will run next?
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| S Jan 28, 2021 at 11:28 | history | suggested | camel | CC BY-SA 4.0 |
added another shortcoming of retrieving the exact remaining time
|
| Jan 27, 2021 at 11:45 | review | Suggested edits | |||
| S Jan 28, 2021 at 11:28 | |||||
| Jun 26, 2019 at 1:14 | comment | added | Alexis Wilke | Ah. I have similar problems. I would use a selected master (using a vote system) and the master sends a message "do maintenance" to computer 1, once computer 1 is done, it reports its new status to the master which then asks computer 2 to do its maintenance, etc. One of those computers would of course be the master, but the code running the maintenance loop should be separate from the actual maintenance. One problem to keep in mind. If your cluster is to grow quite a bit remember that it takes time and it could be so long that some computers do not get updated for a long time! | |
| Jun 26, 2019 at 0:40 | comment | added | Mark Stosberg | Not in my case. I would like to use the exact same configuration on twin hosts, but use AccuracySec= to ensure that both aren't doing maintence at the same time. I would like to see when the timers will actually fire on each host, but can't. | |
| Jun 25, 2019 at 21:10 | comment | added | Alexis Wilke |
Interesting point about the timers. The info we get from list-timers, though, is already pretty good to understand whether your usage of the timers is correct or not.
|
|
| Jun 25, 2019 at 21:00 | history | answered | Mark Stosberg | CC BY-SA 4.0 |