From: Fiona Ebner <f.ebner@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH common 1/2] REST environment: warn helpers: use warn instead of printing to stderr
Date: Mon, 5 Feb 2024 13:28:53 +0100 [thread overview]
Message-ID: <20240205122854.83495-1-f.ebner@proxmox.com> (raw)
Like this, __WARN__ handlers will still be called. In particular,
daemons like pvestatd will set a __WARN__ handler and also log
warnings to syslog. The intention behind introducing log_warn() was to
make warnings more visible, not less, so fix the semantics to make
sure switching from warn to log_warn() does not have this unintended
side-effect.
Reported-by: Friedrich Weber <f.weber@proxmox.com>
Signed-off-by: Fiona Ebner <f.ebner@proxmox.com>
---
src/PVE/RESTEnvironment.pm | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/src/PVE/RESTEnvironment.pm b/src/PVE/RESTEnvironment.pm
index 191c6eb..41efb16 100644
--- a/src/PVE/RESTEnvironment.pm
+++ b/src/PVE/RESTEnvironment.pm
@@ -723,7 +723,7 @@ sub log_warn {
$rest_env->warn($message);
} else {
chomp($message);
- print STDERR "WARN: $message\n";
+ warn "WARN: $message\n";
}
}
@@ -732,7 +732,7 @@ sub warn {
chomp($message);
- print STDERR "WARN: $message\n";
+ warn "WARN: $message\n";
$self->{warning_count}++;
}
--
2.39.2
next reply other threads:[~2024-02-05 12:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-05 12:28 Fiona Ebner [this message]
2024-02-05 12:28 ` [pve-devel] [RFC common 2/2] REST environment: fork worker: install custom __WARN__ handler Fiona Ebner
2024-02-05 12:39 ` Thomas Lamprecht
2024-02-05 13:08 ` Fiona Ebner
2024-02-05 12:38 ` [pve-devel] [PATCH common 1/2] REST environment: warn helpers: use warn instead of printing to stderr Thomas Lamprecht
2024-02-05 13:08 ` 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=20240205122854.83495-1-f.ebner@proxmox.com \
--to=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 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.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal