From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: Add SOCK_STREAM support for syslog
Date: Fri, 10 Nov 2017 12:14:06 -0500 [thread overview]
Message-ID: <20171110171406.GQ1627@brightrain.aerifal.cx> (raw)
In-Reply-To: <20171110140749.GC15263@port70.net>
On Fri, Nov 10, 2017 at 03:07:49PM +0100, Szabolcs Nagy wrote:
> * Jan Horstmann <J.Horstmann@mittwald.de> [2017-11-10 13:17:31 +0000]:
> > some time ago there was a discussion whether musl-libc's syslog should
> > support SOCK_STREAM as a fall back if SOCK_DGRAM fails like glibc does
> > ( http://www.openwall.com/lists/musl/2015/08/10/1 )
> > Later on a patch was posted to the mailing list: http://www.openwall.com/lists/musl/2017/08/21/3
> > Since we depend on this functionality we have applied this patch and are quiet happy with it.
> > I would like to know whether there are any plans to incorporate this patch into a future release?
>
> i think you need to explain why you depend on this
> to get consensus on the inclusion of the patch.
Is it mutually exclusive whether /dev/log is listening as SOCK_DGRAM
or SOCK_STREAM? If not, I think there's a race where connecting to
SOCK_DGRAM fails, then syslogd starts listening on both, and the
SOCK_STREAM connect succeeds in the fallback despite there being a
SOCK_DGRAM service available. Adoption of the patch is mainly blocked
on establishing that it does not harm any existing usage. I suspect
and seem to remember (but haven't looked at it lately) that
SOCK_STREAM has some undesirable properties from a standpoint of
logging and that SOCK_DGRAM is what you want if possible.
Rich
next prev parent reply other threads:[~2017-11-10 17:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-10 13:17 Jan Horstmann
2017-11-10 14:07 ` Szabolcs Nagy
2017-11-10 17:14 ` Rich Felker [this message]
2017-11-11 0:29 ` Laurent Bercot
2017-11-11 0:41 ` Rich Felker
2017-11-11 1:29 ` Laurent Bercot
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=20171110171406.GQ1627@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=musl@lists.openwall.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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).