From: "J.R. Oldroyd" <wgrd@opal.com>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Logging
Date: Tue, 17 Mar 2020 08:37:17 +0100 [thread overview]
Message-ID: <20200317083717.14719676@opal.com> (raw)
In-Reply-To: <CAHmME9onNwD9+hw2LgzZg_OqN21mOPEyQ9wAsFGjTA6=mK7xgA@mail.gmail.com>
On Mon, 16 Mar 2020 13:30:17 -0600 "Jason A. Donenfeld" <Jason@zx2c4.com> wrote:
>
> Adding direct syslog support might make sense. I'll look into
> integrating those files you sent, though, perhaps it'd be better if
> you submitted those as a patch to the mailing list with a proper
> Signed-off-by line? (Or even to Github?)
>
Will do.
> I'm curious to know: is there a reason why you prefer this to something like:
>
> `LOG_LEVEL=debug wireguard-go -f wg0 2>&1 | logger &`
>
Since adding syslog support is so trivial, given the existing code
is already designed around logging levels and given Go's clean support
of syslog, why not just build it in so that wireguard's logging is done
consistently with all other UNIX daemons? Piping stdout to logger
is non-standard and also loses the ability to filter the different
log levels to different log destinations.
-jr
next prev parent reply other threads:[~2020-03-17 17:23 UTC|newest]
Thread overview: 49+ 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 ` J.R. Oldroyd [this message]
2020-03-17 18:12 ` Logging Luis Ressel
2020-03-18 8:14 ` Logging J.R. Oldroyd
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
-- strict thread matches above, loose matches on Subject: below --
2011-04-17 23:30 Logging Zenon Panoussis
2011-04-18 0:53 ` Logging Colin McCabe
2011-04-18 10:13 ` Logging Zenon Panoussis
2011-04-18 17:16 ` Logging Colin McCabe
2011-04-18 18:17 ` Logging Zenon Panoussis
2011-04-18 18:41 ` Logging Colin McCabe
2011-04-18 20:56 ` Logging Zenon Panoussis
2011-04-18 22:25 ` Logging Colin McCabe
2011-04-19 0:10 ` Logging Zenon Panoussis
2011-04-19 5:02 ` Logging Sage Weil
2011-04-19 11:19 ` Logging Zenon Panoussis
2011-04-19 16:27 ` Logging Sage Weil
2005-08-11 15:49 Logging Svenne Krap
2005-08-11 20:54 ` Logging Chris Brenton
2005-08-12 6:24 ` Logging Grant Taylor
2004-04-25 15:32 logging IT Clown
2004-04-25 15:45 ` logging Antony Stone
2004-04-12 3:13 logging ip tables
2004-04-01 5:38 logging IT Clown
2004-04-06 10:26 ` logging D. Prima Prayudi
2004-03-31 9:18 logging IT Clown
2004-03-31 9:59 ` logging Mark Page
2004-03-15 15:56 Logging Hurley, Michael
2004-03-15 15:51 Logging Mario Udina
2004-03-15 16:07 ` Logging Frederic de Villamil
2004-03-15 16:08 ` Logging Antony Stone
2004-03-15 16:25 ` Logging Frank Gruellich
2004-03-15 16:36 ` Logging forum
2003-12-29 22:43 logging John T. Williams
2003-12-30 2:39 ` logging caszonyi
2003-12-30 2:44 ` logging Ray Olszewski
2003-03-24 14:02 logging Philippe Dhont (Sea-ro)
2003-01-14 18:23 Logging Subba Rao
2003-01-16 19:20 ` Logging Athan
2003-01-17 4:26 ` Logging Dharmendra.T
[not found] <20021021210421.79305.qmail@web40702.mail.yahoo.com>
2002-10-21 21:39 ` Logging Antony Stone
2002-04-10 5:46 Logging Chris Rose
2002-04-10 6:08 ` Logging Richard Adams
2002-04-10 6:36 ` Logging Chris Rose
2002-04-10 18:23 ` Logging Richard Adams
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=20200317083717.14719676@opal.com \
--to=wgrd@opal.com \
--cc=Jason@zx2c4.com \
--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 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.