From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-1.0 required=5.0 tests=MAILING_LIST_MULTI, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 6822 invoked from network); 4 Dec 2023 00:40:06 -0000 Received: from alyss.skarnet.org (95.142.172.232) by inbox.vuxu.org with ESMTPUTF8; 4 Dec 2023 00:40:06 -0000 Received: (qmail 41347 invoked by uid 89); 4 Dec 2023 00:40:31 -0000 Mailing-List: contact supervision-help@list.skarnet.org; run by ezmlm Sender: Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Received: (qmail 41340 invoked from network); 4 Dec 2023 00:40:31 -0000 From: "Laurent Bercot" To: "Mr Rini" , supervision@list.skarnet.org Subject: Re: OpenVPN runit service flooding tty Date: Mon, 04 Dec 2023 00:40:03 +0000 Message-Id: In-Reply-To: References: Reply-To: "Laurent Bercot" User-Agent: eM_Client/9.2.2157.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable >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=20 - 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