supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: Jan Braun <janbraun@gmx.de>
To: Laurent Bercot <ska-supervision@skarnet.org>
Cc: Mr Rini <wastelander1972@gmail.com>, supervision@list.skarnet.org
Subject: Re: OpenVPN runit service flooding tty
Date: Tue, 5 Dec 2023 08:29:25 +0100	[thread overview]
Message-ID: <ZW7RVQtjRYR5i_gX@abakus> (raw)
In-Reply-To: <em783517f5-4f39-4f2f-b9e8-a3f4b277bf3c@e23db244.com>

[-- Attachment #1: Type: text/plain, Size: 671 bytes --]

Laurent Bercot schrob:
> IIRC, 1. is intrinsic to runit, there is no way to redirect the default
> logging, [...]

There is: the default logging simply goes to runsvdir's stdout. You can
connect that in /etc/runit/2 to wherever you like.

> a runit service should use the runit logging facility. That is something
> you should report and suggest to the maintainer of the openvpn service
> in Artix.

I couldn't test easily whether openvpn logs to stdout or stderr, but
that's a common pitfall: runit expects logging output on stdout. Thus
a <servicename>/run file should usually include a "exec 2>&1" line to
ensure logs actually go to the log service.

regards,
    Jan

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2023-12-05  7:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAH5fFJp+rKgj2CUdeTiKdijWFzRKa4O8HG-Qw-0D=xojPCWEew@mail.gmail.com>
2023-12-03 21:22 ` Mr Rini
2023-12-04  0:40   ` Laurent Bercot
2023-12-05  7:29     ` Jan Braun [this message]

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=ZW7RVQtjRYR5i_gX@abakus \
    --to=janbraun@gmx.de \
    --cc=ska-supervision@skarnet.org \
    --cc=supervision@list.skarnet.org \
    --cc=wastelander1972@gmail.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).