this is mentioned in the `systemd.time(7)` manpage, but adding it here to should give it more exposure. it's very handy and hopefully avoids some frustration for users less familiar with calendar events.
Signed-off-by: Shannon Sterz <s.st...@proxmox.com> --- calendar-events.adoc | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/calendar-events.adoc b/calendar-events.adoc index 4112f1e..f46f589 100644 --- a/calendar-events.adoc +++ b/calendar-events.adoc @@ -58,6 +58,11 @@ First are hours, then minutes. Hours can be omitted if not needed. In this case `'*'` is assumed for the value of hours. The valid range for values is `0-23` for hours and `0-59` for minutes. +NOTE: You can use `systemd-analyze calendar` to see whether a given calendar +event specification is valid and when it would be triggered next. By passing the +`--iterations=<N>` flag you can also let it output the next `<N>` times the +calendar event would trigger (you need to replace `<N>` with a valid integer). + [[pvesr_schedule_format_examples]] Examples: ~~~~~~~~~ -- 2.39.5 _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
