Re: Re: [PATCH] add SOCK_STREAM support for syslog

["Laurent Bercot" <ska-dietlibc@skarnet.org>]

>Yes, and it never really concluded. I think it's probably harmless to
>support SOCK_STREAM if users want it though.

  I do want it. It's the first step towards a simple, non-bloated
implementation of syslogd. Please support SOCK_STREAM whenever there's
nothing more urgent to do. :P


>One question I had that never got answered: are SOCK_DGRAM and
>SOCK_STREAM unix socket addresses mutually exclusive, or can the same
>name be listening as both types?

  They appear to be mutually exclusive.

execve("./test-socket", ["./test-socket"], [/* 24 vars */]) = 0
arch_prctl(ARCH_SET_FS, 0x602538) = 0
set_tid_address(0x602570) = 9828
socket(PF_LOCAL, SOCK_STREAM|SOCK_NONBLOCK, 0) = 3
setsockopt(3, SOL_SOCKET, SO_REUSEADDR, [1], 4) = 0
socket(PF_LOCAL, SOCK_DGRAM|SOCK_NONBLOCK, 0) = 4
setsockopt(4, SOL_SOCKET, SO_REUSEADDR, [1], 4) = 0
unlink("/tmp/socket") = 0
bind(3, {sa_family=AF_LOCAL, sun_path="/tmp/socket"}, 110) = 0
bind(4, {sa_family=AF_LOCAL, sun_path="/tmp/socket"}, 110) = -1 
EADDRINUSE (Address already in use)

--
  Laurent