supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: "Scott Colby" <scott@scolby.com>
To: supervision@list.skarnet.org
Subject: Re: Understanding the syslogd-linux Service Script
Date: Sat, 12 Sep 2020 02:42:40 -0400	[thread overview]
Message-ID: <0fa6bc96-3e7a-4622-bcf7-4a7d66d3c6be@www.fastmail.com> (raw)
In-Reply-To: <ema5a2fc6e-1f09-4867-96af-516b74f59663@elzian>

Dear Colin and Laurent,

Thank you for the thorough explanations it took me a minute with a
pen and paper to work out the fd movements, but it makes sense to
me now.

My particular environment uses glibc, so the old version of the
example seems to work well. I omit the syslog service's log directory
and the log lines appear on my container's stdout, which was my
goal.

I tried out Colin's SOCK_DGRAM version, but this was unsuccessful;
I received this line at a very high rate (20k lines in just a second
or two) on my stdout:

s6-ipcserverd: warning: unable to accept: Operation not supported

The s6-ipcserverd docs specifically state that it expects a bound
and listening SOCK_STREAM socket, and this led me to the `ipc_accept()`
call that the program makes. Out of curiosity, is there another
s6-family program that handles SOCK_DGRAM sockets? Otherwise, I'll
look in to socklog as Laurent suggested.

Thanks,
Scott

  reply	other threads:[~2020-09-12  6:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-08 16:53 Scott Colby
2020-09-08 18:15 ` Colin Booth
2020-09-08 18:43 ` Colin Booth
2020-09-09  8:01   ` Laurent Bercot
2020-09-12  6:42     ` Scott Colby [this message]
2020-09-12 10:08       ` Laurent Bercot
2020-09-12 10:14       ` Laurent Bercot
2020-09-12 17:59         ` Scott Colby

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=0fa6bc96-3e7a-4622-bcf7-4a7d66d3c6be@www.fastmail.com \
    --to=scott@scolby.com \
    --cc=supervision@list.skarnet.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).