From: Fiona Ebner <f.ebner@proxmox.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: qemu-devel@nongnu.org, pbonzini@redhat.com, hreitz@redhat.com,
t.lamprecht@proxmox.com, d.csapak@proxmox.com
Subject: Re: [PATCH] vl: change PID file path resolve error to warning
Date: Fri, 28 Oct 2022 09:11:57 +0200 [thread overview]
Message-ID: <6fdd4b06-4c9b-5a7c-d16d-c3b362fecb81@proxmox.com> (raw)
In-Reply-To: <Y1p22/LxBASPUTcV@redhat.com>
Am 27.10.22 um 14:17 schrieb Daniel P. Berrangé:
> On Thu, Oct 27, 2022 at 12:14:43PM +0200, Fiona Ebner wrote:
>> + warn_report("not removing PID file on exit: cannot resolve PID file"
>> + " path: %s: %s", pid_file, strerror(errno));
>> + return;
>> }
>
> I don't think using warn_report is desirable here.
>
> If the behaviour of passing a pre-unlinked pidfile is considered
> valid, then we should allow it without printing a warning every
> time an application does this.
>
> warnings are to highlight non-fatal mistakes by applications, and
> this is not a mistake, it is intentionally supported behaviour.
>
> With regards,
> Daniel
But what if the path resolution fails in a scenario where the caller did
not pre-unlik the PID file? Should the warning only be printed when the
errno is not ENOENT? Might still not be accurate in all cases though.
Best Regards,
Fiona
next prev parent reply other threads:[~2022-10-28 7:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-27 10:14 [PATCH] vl: change PID file path resolve error to warning Fiona Ebner
2022-10-27 12:06 ` Hanna Reitz
2022-10-27 12:17 ` Daniel P. Berrangé
2022-10-28 7:11 ` Fiona Ebner [this message]
2022-10-28 7:26 ` Thomas Lamprecht
2022-10-28 7:54 ` Fiona Ebner
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=6fdd4b06-4c9b-5a7c-d16d-c3b362fecb81@proxmox.com \
--to=f.ebner@proxmox.com \
--cc=berrange@redhat.com \
--cc=d.csapak@proxmox.com \
--cc=hreitz@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=t.lamprecht@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;
as well as URLs for NNTP newsgroup(s).