From: Christian Ebner <c.ebner@proxmox.com>
To: pbs-devel@lists.proxmox.com
Subject: [pbs-devel] [PATCH proxmox-backup 0/3] backup client progress log interval
Date: Mon, 21 Oct 2024 14:55:19 +0200 [thread overview]
Message-ID: <20241021125522.237273-1-c.ebner@proxmox.com> (raw)
These patches allow to specify a time based or size based interval
for progress log output as generated during `proxmox-backup-client
backup` runs.
The client is extended by an optional `progress-log-interval`
parameter, which allows to set the interval as `TimeSpan` or
`HumanByte` parsable input string, depending on the variant prefix.
If set to `none` the progress log output is disabled, if no prefix is
specified, a time based interval is assumed. Lastly, if the parameter
is not given, the default 'time:1m' is used.
Examples for client invocations are:
- no progress logging:
`proxmox-backup-client backup root.pxar:/ --progress-log-interval=none`
- time based progress logging with 1min 30s interval
`proxmox-backup-client backup root.pxar:/ --progress-log-interval="1m 30s"`
`proxmox-backup-client backup root.pxar:/ --progress-log-interval="time:1m 30s"`
- size based progress logging with 512MiB interval
`proxmox-backup-client backup root.pxar:/ --progress-log-interval="size:512MiB"`
Lower limits are set to 1s and 100MiB for the corresponding variant in
order to prevent excessive log output.
Christian Ebner (3):
api-types: client: add type to specify progress log interval
client: progress log: factor out log message generation
client: progress log: allow to specify backup log interval
pbs-api-types/src/client.rs | 73 ++++++++++++++++++++++++
pbs-api-types/src/lib.rs | 3 +
pbs-client/src/backup_writer.rs | 92 +++++++++++++++++++++++++------
proxmox-backup-client/src/main.rs | 27 ++++++++-
4 files changed, 174 insertions(+), 21 deletions(-)
create mode 100644 pbs-api-types/src/client.rs
--
2.39.5
_______________________________________________
pbs-devel mailing list
pbs-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel
next reply other threads:[~2024-10-21 12:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-21 12:55 Christian Ebner [this message]
2024-10-21 12:55 ` [pbs-devel] [PATCH proxmox-backup 1/3] api-types: client: add type to specify " Christian Ebner
2024-10-21 12:55 ` [pbs-devel] [PATCH proxmox-backup 2/3] client: progress log: factor out log message generation Christian Ebner
2024-10-21 12:55 ` [pbs-devel] [PATCH proxmox-backup 3/3] client: progress log: allow to specify backup log interval Christian Ebner
2024-10-21 15:08 ` [pbs-devel] [PATCH proxmox-backup 0/3] backup client progress " Thomas Lamprecht
2024-10-21 16:06 ` Christian Ebner
2024-10-22 5:35 ` Thomas Lamprecht
2024-10-23 9:12 ` Christian Ebner
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=20241021125522.237273-1-c.ebner@proxmox.com \
--to=c.ebner@proxmox.com \
--cc=pbs-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.