From mboxrd@z Thu Jan 1 00:00:00 1970
Return-Path: <pve-devel-bounces@lists.proxmox.com>
Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68])
by lore.proxmox.com (Postfix) with ESMTPS id 6798D1FF162
for <inbox@lore.proxmox.com>; Sat, 22 Mar 2025 16:31:23 +0100 (CET)
Received: from firstgate.proxmox.com (localhost [127.0.0.1])
by firstgate.proxmox.com (Proxmox) with ESMTP id 5D5FA3C646;
Sat, 22 Mar 2025 16:31:05 +0100 (CET)
To: pve-devel@lists.proxmox.com
Date: Sun, 23 Mar 2025 00:17:16 +0900
In-Reply-To: <20250322152004.1646886-1-jing@jing.rocks>
References: <20250322152004.1646886-1-jing@jing.rocks>
MIME-Version: 1.0
Message-ID: <mailman.93.1742657463.359.pve-devel@lists.proxmox.com>
List-Id: Proxmox VE development discussion <pve-devel.lists.proxmox.com>
List-Post: <mailto:pve-devel@lists.proxmox.com>
From: Jing Luo via pve-devel <pve-devel@lists.proxmox.com>
Precedence: list
Cc: Jing Luo <jing@jing.rocks>
X-Mailman-Version: 2.1.29
X-BeenThere: pve-devel@lists.proxmox.com
List-Subscribe: <https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel>,
<mailto:pve-devel-request@lists.proxmox.com?subject=subscribe>
List-Unsubscribe: <https://lists.proxmox.com/cgi-bin/mailman/options/pve-devel>,
<mailto:pve-devel-request@lists.proxmox.com?subject=unsubscribe>
List-Archive: <http://lists.proxmox.com/pipermail/pve-devel/>
Reply-To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
List-Help: <mailto:pve-devel-request@lists.proxmox.com?subject=help>
Subject: [pve-devel] [PATCH pve-firewall] tree-wide: change /var/run to /run
and /var/lock to /run/lock
Content-Type: multipart/mixed; boundary="===============8044905637637976736=="
Errors-To: pve-devel-bounces@lists.proxmox.com
Sender: "pve-devel" <pve-devel-bounces@lists.proxmox.com>
--===============8044905637637976736==
Content-Type: message/rfc822
Content-Disposition: inline
Return-Path: <jing@jing.rocks>
X-Original-To: pve-devel@lists.proxmox.com
Delivered-To: pve-devel@lists.proxmox.com
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 2EEFDC944C
for <pve-devel@lists.proxmox.com>; Sat, 22 Mar 2025 16:31:03 +0100 (CET)
Received: from firstgate.proxmox.com (localhost [127.0.0.1])
by firstgate.proxmox.com (Proxmox) with ESMTP id B9BDE3C363
for <pve-devel@lists.proxmox.com>; Sat, 22 Mar 2025 16:30:32 +0100 (CET)
Received: from mail-gw3.jing.rocks (mail-gw3.jing.rocks [219.117.250.209])
(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 <pve-devel@lists.proxmox.com>; Sat, 22 Mar 2025 16:30:31 +0100 (CET)
Received: from mail-gw3.jing.rocks (localhost [127.0.0.1])
by mail-gw3.jing.rocks (Proxmox) with ESMTP id CE3AE165EA
for <pve-devel@lists.proxmox.com>; Sun, 23 Mar 2025 00:20:21 +0900 (JST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jing.rocks; h=cc
:cc:content-transfer-encoding:date:from:from:in-reply-to
:message-id:mime-version:references:reply-to:subject:subject:to
:to; s=mail-gw; bh=ZrbqwlIK3ihdvXyhPhuI7Ytdj0c6yRuD/heKqMnVbic=; b=
PveKFdjpqBFuJA12VA1H2QAqAjqST20V51HBcaY1KUPIkYecPRWwA0JuGwxoBJs8
U2Vw+iLROusyjhKwARvrlD3LGUL2kAkBcu5xai8t3jHJtMc5d9Iz74rzDQl/0oZC
TufLVsAIrZMsUVwnLVjG598icqCbEdv0yYeD3Mo3bo8gxTRKhYitw7XiTYNdea4o
j/EKswqLJBIJmCDC6vw2FHatPTZiRdwWxoOzt5oubC6+QS2s8Sm6o9SYc7T2E3h2
Zwmv9jh3taq3einEKAmj5zMZUPvmq251h88IOZJ0OCn7LqYnYUTGXTJxa+iNgilp
YEeZDdq8CzZK0/RAVywN4g==
Received: from mail.jing.rocks (mail.jing.rocks [192.168.0.222])
(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256)
(No client certificate requested)
by mail-gw3.jing.rocks (Proxmox) with ESMTPS id E4985164ED
for <pve-devel@lists.proxmox.com>; Sun, 23 Mar 2025 00:20:20 +0900 (JST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=jing.rocks;
s=default; t=1742656820;
bh=md3st2fbqAyk5PNs46fg3osCm5LedeqBydCUZq73iFI=;
h=From:To:Cc:Subject:Date:In-Reply-To:References:From;
b=ubr+04yqMeuNd+qQv95l5euP3I1hLbJG9r3Jh7H3iBfqtTelUGGM+kVHWnS557OR6
sGlMHU72DroohE87qYQEXVu00twua66PSeSLmLVL9Xii/OoydfQTDtF8v3EX5XxkoT
ymIbvQTwu8/kOWp5TcTqYSDoMv/5sUz176r7ZV5cSkeWGu2HlDNi1rQYDikbr+gGW0
cWMuIsQjaFjtbQoI/JdGCziOlzcqWGR5lsqxrxRHmVX7UHv/my62uqrEnrdRrw5/b2
SwjG0h2WyXeWlHCjxEOh/rVFFzqR+e0po60vuzYQIkFaxKMvNI3qsURY7RSYOZim39
yGZQ0LkrO7sTA==
Received: from X570AM.jing.rocks (X570AM.lan [IPv6:240b:10:f00:1b00::7e82])
(Authenticated sender: jing@jing.rocks)
by mail.jing.rocks (Postfix) with ESMTPSA id DF7F538203;
Sun, 23 Mar 2025 00:20:20 +0900 (JST)
From: Jing Luo <jing@jing.rocks>
To: pve-devel@lists.proxmox.com
Cc: Jing Luo <jing@jing.rocks>
Subject: [PATCH pve-firewall] tree-wide: change /var/run to /run and /var/lock to /run/lock
Date: Sun, 23 Mar 2025 00:17:16 +0900
Message-ID: <20250322152004.1646886-9-jing@jing.rocks>
X-Mailer: git-send-email 2.49.0
In-Reply-To: <20250322152004.1646886-1-jing@jing.rocks>
References: <20250322152004.1646886-1-jing@jing.rocks>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
X-SPAM-LEVEL: Spam detection results: 0
AWL 0.000 Adjusted score from AWL reputation of From: address
BAYES_00 -1.9 Bayes spam probability is 0 to 1%
DKIM_SIGNED 0.1 Message has a DKIM or DK signature, not necessarily valid
DKIM_VALID -0.1 Message has at least one valid DKIM or DK signature
DKIM_VALID_AU -0.1 Message has a valid DKIM or DK signature from author's domain
DKIM_VALID_EF -0.1 Message has a valid DKIM or DK signature from envelope-from domain
DMARC_PASS -0.1 DMARC pass policy
KAM_INFOUSMEBIZ 0.75 Prevalent use of .info|.us|.me|.me.uk|.biz|xyz|id|rocks|life domains in spam/malware
KAM_OTHER_BAD_TLD 0.75 Other untrustworthy TLDs
SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record
SPF_PASS -0.001 SPF: sender matches SPF record
"/var/run" and "/var/lock" are deprecated.
This is to comply with Debian Policy 9.1.4 "/run and /run/lock".
(https://www.debian.org/doc/debian-policy/ch-opersys.html#run-and-run-lock)
Signed-off-by: Jing Luo <jing@jing.rocks>
---
src/PVE/Firewall.pm | 2 +-
src/pvefw-logger.c | 4 ++--
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/src/PVE/Firewall.pm b/src/PVE/Firewall.pm
index 533f2a2..1445cbd 100644
--- a/src/PVE/Firewall.pm
+++ b/src/PVE/Firewall.pm
@@ -150,7 +150,7 @@ eval {
my $nodename = PVE::INotify::nodename();
my $hostfw_conf_filename = "/etc/pve/nodes/$nodename/host.fw";
-my $pve_fw_lock_filename = "/var/lock/pvefw.lck";
+my $pve_fw_lock_filename = "/run/lock/pvefw.lck";
my $default_log_level = 'nolog'; # avoid logs by default
my $global_log_ratelimit = '--limit 1/sec';
diff --git a/src/pvefw-logger.c b/src/pvefw-logger.c
index f762505..b005046 100644
--- a/src/pvefw-logger.c
+++ b/src/pvefw-logger.c
@@ -77,8 +77,8 @@ Example:
#define LOGFILE "/var/log/pve-firewall.log"
-#define LOCKFILE "/var/lock/pvefw-logger.lck"
-#define PIDFILE "/var/run/pvefw-logger.pid"
+#define LOCKFILE "/run/lock/pvefw-logger.lck"
+#define PIDFILE "/run/pvefw-logger.pid"
#define LOG_CONNTRACK_FILE "/var/lib/pve-firewall/log_nf_conntrack"
#define LQ_LEN 512
--
2.49.0
--===============8044905637637976736==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
--===============8044905637637976736==--