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.1 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,MAILING_LIST_MULTI autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 20221 invoked from network); 12 Sep 2020 18:00:22 -0000 Received: from alyss.skarnet.org (95.142.172.232) by inbox.vuxu.org with ESMTPUTF8; 12 Sep 2020 18:00:22 -0000 Received: (qmail 2639 invoked by uid 89); 12 Sep 2020 18:00:45 -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 2632 invoked from network); 12 Sep 2020 18:00:45 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=scolby.com; h= mime-version:message-id:in-reply-to:references:date:from:to :subject:content-type; s=fm2; bh=6RuqEUIuuOr+jQ/DQphbmC9ACyzfsYp JHf+2ExzC0k8=; b=A6ek6JLcFU2pNdhqnN2nCsyjtlaAE7N5ZENVaSvghwZ7xvs fOMdstAkIXMvtQCSCKh9fHW2UFtzgCYiwUypnaNvebjzHu44zwNS7k32AxEWp8C6 BojGZdOh6fkIjQfYcFXCJ4f04Xno8JhG2/iGwN7SxA74KeIv09dSi+tkWWRFdEv2 ZIkDDhbzzVlUiBgVMcdKAyVVdTZyA5aESiN7ioeyxeLMk5hB3f+LPRnaImmcBxGa XPN4sXftPywLQkmw+hpqCz7CW5Cy9Ndyx2c8EhVfSuWa4StEWPYTJytDBdpkGbUR U+wh3/dVTAFpxco9EmRtHA3UleDvCbmhTc+Dw+A== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=6RuqEU IuuOr+jQ/DQphbmC9ACyzfsYpJHf+2ExzC0k8=; b=Sy99ikn45IEWU4oW5MXYWX 7qwMyUjfvvPtrZGymxCgwWSzrn+L+br9aIw1mqq6GrAK1Fm8cA4g672zzNa2bZo/ aTqvOHI11NoKBYPUaY0X2OyEWsuko+kExfUeNP8JGQFoUyNoXSPIorEhcEoPg8fO z6KlInOuEdY/2dsmCgniIAVIiW9wG++yJb1YWHcqX7TBbretjmHeHLJ44qevN0ku OZm60WJoXO8k2FH6AfMZVo/A0M8Htql3DmXSReKbmpNxMchm2ZtlX23Oslr/bStW nZ1F+3MR26z6GRQTVU2w5ymiRgCxkforylPrBogyi/FWwytK+9M8bQZxMqg6rBaw == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduiedrudeiuddguddvudcutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecunecujfgurhepofgfggfkjghffffhvffutgesth dtredtreertdenucfhrhhomhepfdfutghothhtucevohhlsgihfdcuoehstghothhtsehs tgholhgshidrtghomheqnecuggftrfgrthhtvghrnheptddvtefhudffgefhvdfggfetje ejiefghfevhefgteeffefgkeekgeelfeehjeeinecuvehluhhsthgvrhfuihiivgeptden ucfrrghrrghmpehmrghilhhfrhhomhepshgtohhtthesshgtohhlsgihrdgtohhm X-ME-Proxy: X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.3.0-259-g88fbbfa-fm-20200903.003-g88fbbfa3 Mime-Version: 1.0 Message-Id: <516a8d72-c0c2-4e29-bc10-223ab6e817d4@www.fastmail.com> In-Reply-To: References: <20200908184318.GB15636@cathexis.xen.prgmr.com> <0fa6bc96-3e7a-4622-bcf7-4a7d66d3c6be@www.fastmail.com> Date: Sat, 12 Sep 2020 13:59:55 -0400 From: "Scott Colby" To: supervision@list.skarnet.org Subject: Re: Understanding the syslogd-linux Service Script Content-Type: text/plain > There is not, because the UCSPI model - the one that s6-ipcserver implements - is about handling data *streams*, and forking a child to handle each separate client (as the venerable inetd does). That makes sense to me. > If your goal is to have syslog messages appear on your container's > stdout, then you should actually be able to get away with not having > any syslogd service at all, which is always the preferred solution! That is my goal and it's interesting that I didn't observe the logs ending up on the container's stdout. I was considering that the program I want to run (OpenDNSSEC, to be exact) does something funny that would prevent this when I came across an undocumented configuration option that allows logging to a file or stdout instead of using syslog. I have to sigh, for this is not the first time I've had to read the source of this program in order to figure out what is going on. In any case, thank you for all the explanation. I'm certain my improved understanding of both s6 and syslog will come in handy in the future. Scott