From: Roland <devzero@web.de>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Bug 5177 - got inotify poll request in wrong process
Date: Fri, 18 Sep 2026 18:49:28 +0200 [thread overview]
Message-ID: <dc701a1d-a293-40dc-ab84-b32e263aae80@web.de> (raw)
regarding https://bugzilla.proxmox.com/show_bug.cgi?id=5177 ,
what about this one ?
root@s740:/usr/share/perl5# diff -Naur PVE/APIServer/AnyEvent.pm.bak
PVE/APIServer/AnyEvent.pm
--- PVE/APIServer/AnyEvent.pm.bak 2026-09-08 19:40:05.137690089 +0200
+++ PVE/APIServer/AnyEvent.pm 2026-09-18 18:48:54.443095627 +0200
@@ -1847,6 +1847,8 @@
exit(0);
}
+ PVE::INotify::inotify_close();
+
# else we need to wait until all open connections gets closed
my $w;
$w = AnyEvent->timer(
reply other threads:[~2026-09-21 7:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=dc701a1d-a293-40dc-ab84-b32e263aae80@web.de \
--to=devzero@web.de \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.