From: Graeme Seaton <lists@graemes.com>
To: Thomas Lamprecht <t.lamprecht@proxmox.com>,
Dietmar Maurer <dietmar@proxmox.com>,
Proxmox Backup Server development discussion
<pbs-devel@lists.proxmox.com>
Subject: Re: [pbs-devel] Verify, Prune & GC sequence
Date: Sat, 31 Oct 2020 08:27:42 +0000 [thread overview]
Message-ID: <f3dfe13c-e74a-d698-8eca-b7e18819076c@graemes.com> (raw)
In-Reply-To: <cb988664-095a-61d0-294c-4538443c5fad@proxmox.com>
Thank you both for the links - tested last night and worked great. My
bad on manually editing the schedule - didn't find it immediately
obvious that I could edit the value in the dropbox.
Would also congratulate you all on the project - it is looking really
nice and the UI has come along in leaps and bounds :-D
On 31/10/2020 06:53, Thomas Lamprecht wrote:
> On 31.10.20 07:43, Dietmar Maurer wrote:
>>>> Thanks for the reply - didn't really want stay up to midnight to check ;-) At the moment, scheduling only allows daily (which is invoked at 00:00). If (when?) I can specify custom times then I'll probably use the sequence you described.
>>>>
>>> You can already specify custom times, just edit it, "daily" is just set as default
>>> when creating a new job.
>>>
>> To make it more clear, we support systemd Calendar events. For format details see:
>>
>> https://www.freedesktop.org/software/systemd/man/systemd.time.html#Calendar%20Events
>>
> Here the link to our docs, as we support only the relevant features of Calendar Events:
>
> https://pbs.proxmox.com/docs/calendarevents.html
>
>
prev parent reply other threads:[~2020-10-31 8:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-30 9:31 Graeme Seaton
2020-10-30 11:09 ` Thomas Lamprecht
2020-10-30 16:31 ` Graeme Seaton
2020-10-30 17:17 ` Thomas Lamprecht
2020-10-31 6:43 ` Dietmar Maurer
2020-10-31 6:53 ` Thomas Lamprecht
2020-10-31 8:27 ` Graeme Seaton [this message]
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=f3dfe13c-e74a-d698-8eca-b7e18819076c@graemes.com \
--to=lists@graemes.com \
--cc=dietmar@proxmox.com \
--cc=pbs-devel@lists.proxmox.com \
--cc=t.lamprecht@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.