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 autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 7513 invoked from network); 20 Jan 2021 09:15:42 -0000 Received: from alyss.skarnet.org (95.142.172.232) by inbox.vuxu.org with ESMTPUTF8; 20 Jan 2021 09:15:42 -0000 Received: (qmail 30828 invoked by uid 89); 20 Jan 2021 09:16:04 -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 30821 invoked from network); 20 Jan 2021 09:16:03 -0000 From: "Laurent Bercot" To: supervision@list.skarnet.org Subject: Re: What extra logging utilities are needed with s6? Date: Wed, 20 Jan 2021 09:15:37 +0000 Message-Id: In-Reply-To: References: <20210120065638.embzr5fusyn6xzwl@frisbee> Reply-To: "Laurent Bercot" User-Agent: eM_Client/8.1.979.0 Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable X-VR-SPAMSTATE: OK X-VR-SPAMSCORE: 0 X-VR-SPAMCAUSE: gggruggvucftvghtrhhoucdtuddrgeduledruddvgddtvdcutefuodetggdotffvucfrrhhofhhilhgvmecupfgfoffgtffkveetuefngfdpqfgfvfenuceurghilhhouhhtmecufedttdenucenucfjughrpefhvffufffkjghfrhgfgggtgfesthhqredttderjeenucfhrhhomhepfdfnrghurhgvnhhtuceuvghrtghothdfuceoshhkrgdqshhuphgvrhhvihhsihhonhesshhkrghrnhgvthdrohhrgheqnecuggftrfgrthhtvghrnhepgfeufeeiffevleelkeettedtteetgfevvdfffeejudffjeeijeetfeduueekgeefnecuffhomhgrihhnpehsmhgrrhguvghnrdhorhhgnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmohguvgepshhmthhpohhuth >If all your services support logging to stdout/stderr you can get away wit= hout a syslog service. Instead of a single logging service consuming logs f= rom all other services s6 is designed to connect each long running service= with its own tiny dedicated logging service. To add to this: it is likely that you *still* need a kind of syslogd, because chances are that not all daemons on your systems have been patched/configured/... to write to stderr instead of using syslog(). So, just in case, you should probably have a syslogd running, to catch everything that still uses syslog() - and potentially help you reconfigure the relevant daemons to use stderr instead. When there is nothing left in your syslogd output, you can remove the syslogd service. The stock syslogd from your distribution will do just fine. Optional, advanced stuff if you'd rather use something more s6-idiomatic than your stock syslogd: download socklog. http://smarden.org/socklog/ socklog's documentation says it was made to work with runit, but it will work with s6 as well. What it does is listen to the /dev/log socket, convert the syslog priority to text, and just send the log message to its stdout. So you can process that output via s6-log just like you would with any other service running under s6, and have it stored and automatically rotated just like any other service, without the need for logrotate. -- Laurent