From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate001.proxmox.com (gate001.proxmox.com [45.144.208.40]) by lore.proxmox.com (Postfix) with ESMTPS id E36761FF0BC for ; Fri, 21 Aug 2026 09:09:47 +0200 (CEST) Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1]) by gate001.proxmox.com (Proxmox) with ESMTP id A244221588; Fri, 21 Aug 2026 09:09:47 +0200 (CEST) Message-ID: <3648a43f-8932-414a-ae99-7bd2229bd34b@proxmox.com> Date: Fri, 21 Aug 2026 09:09:43 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [RFC] Centralized management for standalone PBS file clients To: Ciro Iriarte References: <6a78d7fc.4987c784.356268.046f@mx.google.com> <27a894c0-ce4b-4bfd-855c-b0aef571ab21@proxmox.com> Content-Language: en-US, de-DE From: Christian Ebner In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1787296158246 X-SPAM-LEVEL: Spam detection results: 0 AWL -0.421 Adjusted score from AWL reputation of From: address DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment (newer systems) RCVD_IN_DNSWL_MED -2.3 Sender listed at https://www.dnswl.org/, medium trust SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Message-ID-Hash: NIXWUUQNCS7HUATK23AVP6XHC547EXG2 X-Message-ID-Hash: NIXWUUQNCS7HUATK23AVP6XHC547EXG2 X-MailFrom: c.ebner@proxmox.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header CC: pbs-devel@lists.proxmox.com, Thomas Lamprecht , Lukas Wagner X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox Backup Server development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: Hi, I've discussed this internally and we do have some in-house development effort going on with respect to client job scheduling (not public yet). So it probably is best to hold of for a bit longer with your development efforts, and have a look at the code once it is being send for review on the mailing list. I however cannot give you an ETA for that. Best regards, Chris