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 [IPv6:2a01:7e0:0:424::9])
	by lore.proxmox.com (Postfix) with ESMTPS id 325541FF13F
	for <inbox@lore.proxmox.com>; Thu, 07 May 2026 12:17:04 +0200 (CEST)
Received: from firstgate.proxmox.com (localhost [127.0.0.1])
	by firstgate.proxmox.com (Proxmox) with ESMTP id 0EBA712E2D;
	Thu,  7 May 2026 12:17:04 +0200 (CEST)
Date: Thu, 7 May 2026 12:16:26 +0200
From: Wolfgang Bumiller <w.bumiller@proxmox.com>
To: Fiona Ebner <f.ebner@proxmox.com>
Subject: applied: [PATCH container 1/3] pct: unlock: log that operation
 happened to syslog
Message-ID: <g3vhosly7y2apps6c3zzal7gafm7xk4pds2dd2kwqi34uzwvtb@misol5zvejhf>
References: <20260427112255.369695-1-f.ebner@proxmox.com>
 <20260427112255.369695-2-f.ebner@proxmox.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20260427112255.369695-2-f.ebner@proxmox.com>
X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2
X-Bm-Transport-Timestamp: 1778148878248
X-SPAM-LEVEL: Spam detection results:  0
	AWL                     0.087 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
Message-ID-Hash: Y2NMOGUAIMPONPS6IK64IWKCIWNMEZCG
X-Message-ID-Hash: Y2NMOGUAIMPONPS6IK64IWKCIWNMEZCG
X-MailFrom: w.bumiller@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: pve-devel@lists.proxmox.com
X-Mailman-Version: 3.3.10
Precedence: list
List-Id: Proxmox VE development discussion <pve-devel.lists.proxmox.com>
List-Help: <mailto:pve-devel-request@lists.proxmox.com?subject=help>
List-Owner: <mailto:pve-devel-owner@lists.proxmox.com>
List-Post: <mailto:pve-devel@lists.proxmox.com>
List-Subscribe: <mailto:pve-devel-join@lists.proxmox.com>
List-Unsubscribe: <mailto:pve-devel-leave@lists.proxmox.com>

applied this one

On Mon, Apr 27, 2026 at 01:22:43PM +0200, Fiona Ebner wrote:
> It can be helpful to see when a container was manually unlocked to
> analyze certain issues when looking at the syslog.
> 
> Signed-off-by: Fiona Ebner <f.ebner@proxmox.com>
> ---
>  src/PVE/CLI/pct.pm | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/src/PVE/CLI/pct.pm b/src/PVE/CLI/pct.pm
> index e2f3c90..9ae4ce4 100755
> --- a/src/PVE/CLI/pct.pm
> +++ b/src/PVE/CLI/pct.pm
> @@ -112,6 +112,8 @@ __PACKAGE__->register_method({
>  
>          PVE::LXC::Config->remove_lock($vmid);
>  
> +        syslog('info', "executed 'pct unlock $vmid'");
> +
>          return undef;
>      },
>  });
> -- 
> 2.47.3