From: Andrew Schulman <schulman.andrew@epa.gov>
To: cygwin@cygwin.com
Subject: Re: socat UDP-LISTEN,fork misbehaves
Date: Tue, 26 Oct 2021 21:48:07 -0400 [thread overview]
Message-ID: <bnbhng5mccdpulc9t4npkom2akebm78foj@4ax.com> (raw)
In-Reply-To: <895fd3a8-2bd8-ffce-2b3b-ba371aba8612@gmail.com>
> I have socat 1.7.4.1-1 and the same version on Linux.
> When I try to create a forking UDP server, only the first client is served, unlike in Linux where subsequent clients are served properly.
>
> Test case. Terminal 1:
>
> socat -v UDP-LISTEN:12345,reuseaddr,fork SYSTEM:"stdbuf -i0 -o0 -e0 sed s/././g"
>
> Terminal 2
>
> ( ( date; sleep 10 ) | socat UDP:127.0.0.1:12345 - & sleep 1; date | socat UDP:127.0.0.1:12345 - )
>
> Expected output in Terminal 2:
>
> ...............................
> ...............................
>
> Actual:
>
> ...............................
>
> Reproducible: amd64, x86, Windows 10, Windows 7
Thanks for reporting. Unfortunately, I have no insight into what might
cause that fault in Cygwin. socat in Cygwin is compiled OOTB, with no
patches. Any debugging or patches would be welcome. Andrew
prev parent reply other threads:[~2021-10-27 1:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-23 16:00 Ilya Basin
2021-10-27 1:48 ` Andrew Schulman [this message]
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=bnbhng5mccdpulc9t4npkom2akebm78foj@4ax.com \
--to=schulman.andrew@epa.gov \
--cc=cygwin@cygwin.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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).