From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Fiona Ebner <f.ebner@proxmox.com>
Subject: Re: [pve-devel] [PATCH v2 qemu] init: daemonize: defuse PID file resolve error to warning
Date: Fri, 28 Oct 2022 09:40:00 +0200 [thread overview]
Message-ID: <aa6d47c2-26e2-d49c-3e89-f83ef5ee3996@proxmox.com> (raw)
In-Reply-To: <20221027081324.55998-1-f.ebner@proxmox.com>
On 27/10/2022 10:13, Fiona Ebner wrote:
> When proxmox-file-restore invokes QEMU, the PID file is a (temporary)
> file that's already unlinked, so resolving the absolute path here
> failed.
>
> It should not be a critical error when the PID file unlink handler
> can't be registered, because the path can't be resolved for whatever
> reason. Just turn it into a warning instead.
thx for the patch!
>
> Reported-by: Dominik Csapak <d.csapak@proxmox.com>
> Suggested-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
> Signed-off-by: Fiona Ebner <f.ebner@proxmox.com>
> ---
>
> Changes from v1:
> * Added R-b and S-b tags.
>
> softmmu/vl.c | 7 +++----
> 1 file changed, 3 insertions(+), 4 deletions(-)
>
> diff --git a/softmmu/vl.c b/softmmu/vl.c
> index 0d233d55f3..1fa992ab09 100644
> --- a/softmmu/vl.c
> +++ b/softmmu/vl.c
> @@ -2445,10 +2445,9 @@ static void qemu_maybe_daemonize(const char *pid_file)
>
> pid_file_realpath = g_malloc0(PATH_MAX);
> if (!realpath(pid_file, pid_file_realpath)) {
> - error_report("cannot resolve PID file path: %s: %s",
> - pid_file, strerror(errno));
> - unlink(pid_file);
> - exit(1);
> + warn_report("not removing PID file on exit: cannot resolve path: "
> + "%s: %s", pid_file, strerror(errno));
As my reply to the upstream patch at Daniel's query w.r.t. to warn,
I'd also like to drop the warning here, at least for ENOENT, which
would cover our, and IMO most other, use cases.
> + return;
> }
>
> qemu_unlink_pidfile_notifier = (struct UnlinkPidfileNotifier) {
prev parent reply other threads:[~2022-10-28 7:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-27 8:13 Fiona Ebner
2022-10-28 7:40 ` Thomas Lamprecht [this message]
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=aa6d47c2-26e2-d49c-3e89-f83ef5ee3996@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=f.ebner@proxmox.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox