all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Shannon Sterz <s.sterz@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH docs] calendar-events: add a note about `systemd-analyze calendar`
Date: Mon, 14 Apr 2025 12:29:49 +0200	[thread overview]
Message-ID: <20250414102948.87726-1-s.sterz@proxmox.com> (raw)

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>
---
 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


                 reply	other threads:[~2025-04-14 10:30 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20250414102948.87726-1-s.sterz@proxmox.com \
    --to=s.sterz@proxmox.com \
    --cc=pve-devel@lists.proxmox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal