From: "Michael Ströder" <michael@stroeder.com>
To: Juliusz Chroboczek <jch@irif.fr>, galene@lists.galene.org
Subject: [Galene] Re: Logging
Date: Thu, 7 Jan 2021 23:45:49 +0100 [thread overview]
Message-ID: <40ad9a1d-c97c-5f01-368d-1ef1862c4d07@stroeder.com> (raw)
In-Reply-To: <875z485swt.wl-jch@irif.fr>
On 1/7/21 10:38 PM, Juliusz Chroboczek wrote:
> It turns out that Pion's logging is controlled by environment variables.
> This is described here:
>
> https://github.com/pion/webrtc/wiki/Debugging-WebRTC
Great!
Not so great for you because I will probably ask more questions. ;-)
> Galène could potentially:
> - set the environment variables;
> - hook into Pion's internals to redirect the log somewhere (to a web page?).
To me it seems the systemd unit can handle all this. See examples below.
Ciao, Michael.
----- /etc/systemd/system/galene.service -----
[Unit]
Description=Galene Videoconferencing Server
Requires=local-fs.target network.target
After=local-fs.target nss-lookup.target time-sync.target
[Service]
Type=simple
EnvironmentFile=-/etc/sysconfig/galene
ExecStart=/usr/sbin/galene $ARGS
User=galene
Group=galene
Restart=on-failure
LimitNOFILE=65536
# redirect stderr and stdout to log file
StandardOutput=append:/var/log/galene/stdout.log
StandardError=append:/var/log/galene/stderr.log
[Install]
WantedBy=multi-user.target
----- /etc/sysconfig/galene -----
# Configure command-line arguments for Galène video conference server
ARGS="-http 0.0.0.0:8444 -data /etc/galene -groups
/var/lib/galene/groups -static /usr/share/galene/static -recordings
/var/lib/galene/recordings"
# pion debug messages set by env vars
#PION_LOG_TRACE="all"
#PION_LOG_DEBUG="all"
PIONS_LOG_INFO="ice"
PIONS_LOG_WARNING="all"
next prev parent reply other threads:[~2021-01-07 22:45 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-07 21:38 [Galene] Logging Juliusz Chroboczek
2021-01-07 22:45 ` Michael Ströder [this message]
2021-01-08 0:35 ` [Galene] Logging Antonin Décimo
2021-01-08 12:40 ` Toke Høiland-Jørgensen
2021-01-08 13:28 ` Juliusz Chroboczek
2021-01-08 13:52 ` Toke Høiland-Jørgensen
2021-01-08 14:33 ` Michael Ströder
2021-01-08 15:13 ` Juliusz Chroboczek
2021-01-08 17:34 ` Michael Ströder
2021-01-08 18:00 ` Juliusz Chroboczek
2021-01-08 15:34 ` Juliusz Chroboczek
2021-01-08 19:34 ` Toke Høiland-Jørgensen
2021-01-08 19:56 ` Juliusz Chroboczek
2021-01-09 0:18 ` Toke Høiland-Jørgensen
2021-01-09 13:34 ` Juliusz Chroboczek
2021-01-10 13:47 ` Toke Høiland-Jørgensen
2021-01-10 15:14 ` [Galene] Congestion control and WebRTC [was: Logging] Juliusz Chroboczek
2021-01-10 15:23 ` [Galene] " Juliusz Chroboczek
2021-01-10 22:23 ` Toke Høiland-Jørgensen
2021-01-10 22:44 ` Dave Taht
2021-01-11 0:07 ` Juliusz Chroboczek
2021-01-11 0:20 ` Toke Høiland-Jørgensen
2021-01-11 0:28 ` Juliusz Chroboczek
2021-01-11 0:30 ` Dave Taht
2021-01-11 6:23 ` Dave Taht
2021-01-11 12:55 ` [Galene] Multichannel audio [was: Congestion control...] Juliusz Chroboczek
2021-01-11 17:25 ` [Galene] " Dave Taht
2021-01-11 13:38 ` [Galene] Re: Congestion control and WebRTC [was: Logging] Juliusz Chroboczek
2021-01-11 15:17 ` Toke Høiland-Jørgensen
2021-01-11 17:20 ` Dave Taht
2021-01-12 1:38 ` Juliusz Chroboczek
2021-01-10 15:17 ` [Galene] Re: Logging Juliusz Chroboczek
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
List information: https://lists.galene.org/postorius/lists/galene.lists.galene.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=40ad9a1d-c97c-5f01-368d-1ef1862c4d07@stroeder.com \
--to=michael@stroeder.com \
--cc=galene@lists.galene.org \
--cc=jch@irif.fr \
/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