From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) by lore.proxmox.com (Postfix) with ESMTPS id 829051FF15F for ; Mon, 21 Oct 2024 14:55:35 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 9BEB2345C2; Mon, 21 Oct 2024 14:56:13 +0200 (CEST) From: Christian Ebner To: pbs-devel@lists.proxmox.com Date: Mon, 21 Oct 2024 14:55:19 +0200 Message-Id: <20241021125522.237273-1-c.ebner@proxmox.com> X-Mailer: git-send-email 2.39.5 MIME-Version: 1.0 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.029 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment RCVD_IN_VALIDITY_CERTIFIED_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_RPBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_SAFE_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Subject: [pbs-devel] [PATCH proxmox-backup 0/3] backup client progress log interval X-BeenThere: pbs-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox Backup Server development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Proxmox Backup Server development discussion Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: pbs-devel-bounces@lists.proxmox.com Sender: "pbs-devel" 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