From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [IPv6:2a01:7e0:0:424::9]) by lore.proxmox.com (Postfix) with ESMTPS id 0F6F51FF17C for ; Wed, 23 Jul 2025 16:40:48 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 584E316471; Wed, 23 Jul 2025 16:42:07 +0200 (CEST) From: Fiona Ebner To: pve-devel@lists.proxmox.com Date: Wed, 23 Jul 2025 16:40:06 +0200 Message-ID: <20250723144131.170616-2-f.ebner@proxmox.com> X-Mailer: git-send-email 2.47.2 In-Reply-To: <20250723144131.170616-1-f.ebner@proxmox.com> References: <20250723144131.170616-1-f.ebner@proxmox.com> MIME-Version: 1.0 X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1753281683834 X-SPAM-LEVEL: Spam detection results: 0 AWL -0.028 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: [pve-devel] [PATCH manager v2 1/4] debian: add tpmfiles.d config to create /run/pve directory X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Proxmox VE development discussion Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: pve-devel-bounces@lists.proxmox.com Sender: "pve-devel" The pve-lxc-syscalld systemd service currently uses /run/pve as a runtime directory. This means, that when the service is restarted, the directory will be recreated. But the /run/pve directory is not just used as the runtime directory of this service, but also for other things, e.g. storage tunnel and mtunnel sockets, container stderr logs as well as pull metric cache and lock, which will be lost when the service is restarted. The plan is to give the service its own runtime directory that is only used for that purpose and nothing else. However, this means the /run/pve directory will not get created automatically anymore (e.g. pull metric relies on the existence already). Add this tmpfiles.d configuration to create it automatically again. Note that the permissions/owner are different now. As the runtime directory, it was created with 0755 root:root. This tmpfiles configuration changes this to 0750 root:root. Signed-off-by: Fiona Ebner --- Changes in v2: * use root:root rather than root:www-data * rely on debhelper v13/dh_installtmpfiles debian/tmpfiles | 2 ++ 1 file changed, 2 insertions(+) create mode 100644 debian/tmpfiles diff --git a/debian/tmpfiles b/debian/tmpfiles new file mode 100644 index 00000000..98b8fb96 --- /dev/null +++ b/debian/tmpfiles @@ -0,0 +1,2 @@ +#Type Path Mode User Group Age Argument +d /run/pve 0750 root root - - -- 2.47.2 _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel