OpenVPN runit service flooding tty

OpenVPN runit service flooding tty

[Mr Rini]

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

Hi, I am using the Artix Linux runit service for OpenVPN, available here:
https://gitea.artixlinux.org/packages/openvpn-runit
However, at boot time the service is throwing a huge output to the tty and
I have to wait it to finish to get to the login prompt (I'm not using a
display manager). As a temporary dirty workaround I have appended the
--syslog option to the exec command, the output being redirected to the
system logger. Is there a cleaner way to change the default behavior?
thanks in advance.

Re: OpenVPN runit service flooding tty

[Laurent Bercot]

>Hi, I am using the Artix Linux runit service for OpenVPN, available here:
>https://gitea.artixlinux.org/packages/openvpn-runit

  Sounds like two compounding problems:
  1. the default logging place for the runit supervision tree is the same
terminal you're using to log in
  2. there is no dedicated logger for the openvpn service.

  IIRC, 1. is intrinsic to runit, there is no way to redirect the default
logging, and that means your console is at the mercy of verbose services 
-
so every service needs a dedicated logger.
  You can use --syslog as a workaround indeed, but 2. should be fixed: 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.

--
  Laurent

Re: OpenVPN runit service flooding tty

[Jan Braun]

[-- 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 --]