From: "Laurent Bercot" <ska-supervision@skarnet.org>
To: supervision@list.skarnet.org
Subject: Re: Understanding the syslogd-linux Service Script
Date: Sat, 12 Sep 2020 10:14:38 +0000 [thread overview]
Message-ID: <embd9096a2-3ead-4a43-a800-2eacd6afa273@elzian> (raw)
In-Reply-To: <0fa6bc96-3e7a-4622-bcf7-4a7d66d3c6be@www.fastmail.com>
>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.
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!
When syslog() can't find a server that listens on /dev/log, it writes
its message to /dev/console. In a container environment, /dev/console
by definition should be your container's stdout. So, not handling
syslog messages in your container at all should naturally make them
fall through to where you want them.
--
Laurent
next prev parent reply other threads:[~2020-09-12 10:14 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
2020-09-12 10:08 ` Laurent Bercot
2020-09-12 10:14 ` Laurent Bercot [this message]
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=embd9096a2-3ead-4a43-a800-2eacd6afa273@elzian \
--to=ska-supervision@skarnet.org \
--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).