From: Fabian Ebner <f.ebner@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [RFC v2 common 2/2] REST environment: allow export of log_warn
Date: Fri, 29 Oct 2021 13:16:23 +0200 [thread overview]
Message-ID: <20211029111624.142116-2-f.ebner@proxmox.com> (raw)
In-Reply-To: <20211029111624.142116-1-f.ebner@proxmox.com>
Signed-off-by: Fabian Ebner <f.ebner@proxmox.com>
---
New in v2.
src/PVE/RESTEnvironment.pm | 3 +++
1 file changed, 3 insertions(+)
diff --git a/src/PVE/RESTEnvironment.pm b/src/PVE/RESTEnvironment.pm
index bf10040..1b2af08 100644
--- a/src/PVE/RESTEnvironment.pm
+++ b/src/PVE/RESTEnvironment.pm
@@ -8,6 +8,7 @@ package PVE::RESTEnvironment;
use strict;
use warnings;
+use Exporter qw(import);
use Fcntl qw(:flock);
use IO::File;
use IO::Handle;
@@ -20,6 +21,8 @@ use PVE::ProcFSTools;
use PVE::SafeSyslog;
use PVE::Tools;
+our @EXPORT_OK = qw(log_warn);
+
my $rest_env;
# save $SIG{CHLD} handler implementation.
--
2.30.2
next prev parent reply other threads:[~2021-10-29 11:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-29 11:16 [pve-devel] [RFC v2 common 1/2] REST environment: add static log_warn function Fabian Ebner
2021-10-29 11:16 ` Fabian Ebner [this message]
2022-03-04 10:33 ` [pve-devel] applied: Re: [RFC v2 common 2/2] REST environment: allow export of log_warn Thomas Lamprecht
2021-10-29 11:16 ` [pve-devel] [RFC v2 container 1/1] print_ct_warn_log: use log_warn function from RESTEnvironment Fabian Ebner
2022-03-04 10:25 ` Thomas Lamprecht
2022-03-04 10:32 ` Fabian Ebner
2022-03-04 10:40 ` Thomas Lamprecht
2022-12-14 8:23 ` Fiona Ebner
2022-12-14 11:14 ` [pve-devel] applied: " Thomas Lamprecht
2022-02-16 7:34 ` [pve-devel] [RFC v2 common 1/2] REST environment: add static log_warn function Fabian Ebner
2022-03-04 10:40 ` [pve-devel] applied: " Thomas Lamprecht
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=20211029111624.142116-2-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.