mirror of
git://git.proxmox.com/git/pve-docs.git
synced 2025-08-02 16:21:55 +03:00
calendar-events: add a note about systemd-analyze calendar
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.sterz@proxmox.com> Link: https://lore.proxmox.com/20250414102948.87726-1-s.sterz@proxmox.com
This commit is contained in:
committed by
Thomas Lamprecht
parent
7d7bb4aed0
commit
dbf3f1c509
@ -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.
|
case `'*'` is assumed for the value of hours.
|
||||||
The valid range for values is `0-23` for hours and `0-59` for minutes.
|
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]]
|
[[pvesr_schedule_format_examples]]
|
||||||
Examples:
|
Examples:
|
||||||
~~~~~~~~~
|
~~~~~~~~~
|
||||||
|
Reference in New Issue
Block a user