J.R. Oldroyd wgrd at opal.com
Wed Mar 18 09:14:42 CET 2020

On Tue, 17 Mar 2020 18:12:05 +0000 Luis Ressel <aranea at 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.


[1] optional syslog logging for wireguard-go
	(both files are needed)

More information about the WireGuard mailing list