From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.sysutils.supervision.general/2607 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: "Laurent Bercot" Newsgroups: gmane.comp.sysutils.supervision.general Subject: Re: Managing difficult log files Date: Fri, 17 May 2019 09:08:10 +0000 Message-ID: References: <2dd0d673-dfbd-f9ff-f5d9-9d2bc4b27464@heuristicsystems.com.au> Reply-To: "Laurent Bercot" Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="121538"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: eM_Client/7.2.34711.0 To: supervision@list.skarnet.org Original-X-From: supervision-return-2197-gcsg-supervision=m.gmane.org@list.skarnet.org Fri May 17 11:07:28 2019 Return-path: Envelope-to: gcsg-supervision@m.gmane.org Original-Received: from alyss.skarnet.org ([95.142.172.232]) by blaine.gmane.org with smtp (Exim 4.89) (envelope-from ) id 1hRYpq-000VSe-OW for gcsg-supervision@m.gmane.org; Fri, 17 May 2019 11:07:26 +0200 Original-Received: (qmail 8901 invoked by uid 89); 17 May 2019 09:07:52 -0000 Mailing-List: contact supervision-help@list.skarnet.org; run by ezmlm Original-Sender: Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Original-Received: (qmail 8894 invoked from network); 17 May 2019 09:07:51 -0000 In-Reply-To: <2dd0d673-dfbd-f9ff-f5d9-9d2bc4b27464@heuristicsystems.com.au> Xref: news.gmane.org gmane.comp.sysutils.supervision.general:2607 Archived-At: >So an intermediate reader appears to be a sound workaround. Does anyone >have a better solution than > >ErrorLog =E2=80=9C|'execlineb =E2=80=93Pc fdmove 1 0 s6-fdholder-retrieve >/s/live/servicedirs/s6rc-fdholder/s =E2=80=98pipe:s6rc-w-final-logger=E2= =80=99 fdswap 0 >1 sh -c "read X; echo ${X}" 1. "cat" should work instead of your shell excerpt, shouldn't it? Isn't it supposed to flush on every line? 2. Instead of spawning a separate process for each ErrorLog, it should be possible to create a fifo, and declare that fifo as your ErrorLog file. Every httpd would then write into the fifo, and you would have a single s6-log reading from it. -- Laurent