From: Mark Geisert <mark@maxrnd.com>
To: cygwin-patches@cygwin.com
Subject: Re: [PATCH v2 0/6] Some AF_UNIX fixes
Date: Wed, 14 Oct 2020 21:19:39 -0700 [thread overview]
Message-ID: <9d20509e-486b-ce79-0701-22557702b2b0@maxrnd.com> (raw)
In-Reply-To: <ea3b1e6a-8857-cd1f-349d-6fc64c2d1b77@cornell.edu>
Ken Brown via Cygwin-patches wrote:
> Are you aware of any test suite that I could run? I've been using examples from
> Kerrisk's book, because that's what I read to learn the basics of sockets. But
> those are just examples and are not meant to be comprehensive.
In ye olden days I used to use Stevens+Rago "Advanced Programming In The Unix
Environment, 2nd ed.". Chapter 17 covers UNIX domain sockets as advanced IPC.
It's more examples but maybe they hit different corners of the playing field. I
don't know of a test suite or even a standalone program that exercises AF_UNIX.
..mark
next prev parent reply other threads:[~2020-10-15 4:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-04 16:49 Ken Brown
2020-10-04 16:49 ` [PATCH v2 1/6] Cygwin: AF_UNIX: use FILE_OPEN_REPARSE_POINT when needed Ken Brown
2020-10-04 16:49 ` [PATCH v2 2/6] Cygwin: fix handling of known reparse points that are not symlinks Ken Brown
2020-10-04 16:49 ` [PATCH v2 3/6] Cygwin: always recognize AF_UNIX sockets as reparse points Ken Brown
2020-10-04 16:49 ` [PATCH v2 4/6] Cygwin: AF_UNIX: socket: set the O_RDWR flag Ken Brown
2020-10-04 16:49 ` [PATCH v2 5/6] Cygwin: AF_UNIX: listen_pipe: check for STATUS_SUCCESS Ken Brown
2020-10-13 11:28 ` Corinna Vinschen
2020-10-13 13:18 ` Ken Brown
2020-10-13 15:31 ` Corinna Vinschen
2020-10-04 16:49 ` [PATCH v2 6/6] Cygwin: AF_UNIX: open_pipe: call recv_peer_info Ken Brown
2020-10-08 21:36 ` [PATCH v2 0/6] Some AF_UNIX fixes Ken Brown
2020-10-13 11:49 ` Corinna Vinschen
2020-10-14 16:39 ` Ken Brown
2020-10-15 4:19 ` Mark Geisert [this message]
2020-10-15 5:48 ` Brian Inglis
2020-10-15 8:16 ` Corinna Vinschen
2020-10-13 11:02 ` Corinna Vinschen
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=9d20509e-486b-ce79-0701-22557702b2b0@maxrnd.com \
--to=mark@maxrnd.com \
--cc=cygwin-patches@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).