From: "J.R. Oldroyd" <wgrd@opal.com>
To: Luis Ressel <aranea@aixah.de>
Cc: "Jason A. Donenfeld" <Jason@zx2c4.com>,
WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Logging
Date: Wed, 18 Mar 2020 09:14:42 +0100 [thread overview]
Message-ID: <20200318091442.0d45889a@opal.com> (raw)
In-Reply-To: <20200317181205.ar7762xdewbszu4q@vega>
On Tue, 17 Mar 2020 18:12:05 +0000 Luis Ressel <aranea@aixah.de> wrote:
>
> If you're adding logging support, I'd prefer logs on stderr over a
> centralized legacy mechanism such as syslog. That's much more flexible;
> in particular, it makes it much easier to direct logs of different
> daemons to different places, or run daemons in chroots.
>
First, I should point out that the whole purpose of syslog(3) is
to do the flexible directing of different daemons' logs to different
places, including in chroots.
That said, adding logging to stderr is also very trivial, given the
current code. I have updated the two files on my website [1] to include
this. Just set environment variable WG_LOG_DEST to "stderr" and then
start wireguard-go.
Please test. If this works as desired, I will update the git patch
that I sent in yesterday.
-jr
[1] optional syslog logging for wireguard-go
http://opal.com/jr/wireguard/logger.go
http://opal.com/jr/wireguard/logger_syslog.go
(both files are needed)
next prev parent reply other threads:[~2020-03-18 8:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-15 13:16 Logging J.R. Oldroyd
2020-03-16 11:25 ` Logging Arti Zirk
2020-03-16 19:30 ` Logging Jason A. Donenfeld
2020-03-17 7:37 ` Logging J.R. Oldroyd
2020-03-17 18:12 ` Logging Luis Ressel
2020-03-18 8:14 ` J.R. Oldroyd [this message]
2020-03-18 10:43 ` Logging Luis Ressel
2020-03-17 10:09 ` [PATCH 0/1] Logging J.R. Oldroyd
2020-03-17 10:09 ` [PATCH 1/1] Add support for logging to syslog(3) on operating systems that support it (i.e., non-Windows, non-Plan9) J.R. Oldroyd
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=20200318091442.0d45889a@opal.com \
--to=wgrd@opal.com \
--cc=Jason@zx2c4.com \
--cc=aranea@aixah.de \
--cc=wireguard@lists.zx2c4.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).