From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id B5997B836C for ; Thu, 7 Mar 2024 14:50:32 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 96436372B0 for ; Thu, 7 Mar 2024 14:50:32 +0100 (CET) Received: from proxmox-new.maurer-it.com (proxmox-new.maurer-it.com [94.136.29.106]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS for ; Thu, 7 Mar 2024 14:50:31 +0100 (CET) Received: from proxmox-new.maurer-it.com (localhost.localdomain [127.0.0.1]) by proxmox-new.maurer-it.com (Proxmox) with ESMTP id 5A3FD4887B; Thu, 7 Mar 2024 14:50:31 +0100 (CET) From: Stefan Lendl To: Gabriel Goller , Proxmox Backup Server development discussion In-Reply-To: References: <20240307133342.198417-2-s.lendl@proxmox.com> Date: Thu, 07 Mar 2024 14:50:30 +0100 Message-ID: <87cys6jgm1.fsf@gmail.com> MIME-Version: 1.0 Content-Type: text/plain X-SPAM-LEVEL: Spam detection results: 0 AWL 0.031 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 SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record T_SCC_BODY_TEXT_LINE -0.01 - Subject: Re: [pbs-devel] [PATCH v2 proxmox-backup 1/1] PruneJobEdit disallow blank schedule value 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: , X-List-Received-Date: Thu, 07 Mar 2024 13:50:32 -0000 "Gabriel Goller" writes: > Hmm it currently doesn't work, but IMO it should be possible to create a > prune-job without a schedule? > So users can run it manually or temporarily disable a prune-job. Yes, I was thinking about that as well. It's currently possible to manually run a prune job via Content > Prune All There you have to add the prune keep parameters for each run. This is not as convenient as if you had an already saved prune job. I would argue that people only run a manual prune job in very specific scenarios like when wanting to free up space. In that case, the user would want to change the keep settings anyway. Prune jobs have an enable checkbox to (temporarily) disable a prune job. One can manually start a disabled prune job. Best regards, Stefan