From: Grant Taylor via TUHS <tuhs@minnie.tuhs.org>
To: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] sockets (was Re: First appearance of named pipes)
Date: Wed, 25 Mar 2020 22:11:03 -0600 [thread overview]
Message-ID: <25956003-d4df-36ab-fd89-37c90bf40a13@spamtrap.tnetconsulting.net> (raw)
In-Reply-To: <alpine.BSF.2.21.9999.2003261331300.34256@aneurin.horsfall.org>
[-- Attachment #1: Type: text/plain, Size: 812 bytes --]
On 3/25/20 8:38 PM, Dave Horsfall wrote:
> Are you trying to set up a loop of processes or something?
Nope. I'll try another way
+------------------+ +-------------+
--(TCP)-->+ socket stdout +---+ stdin |
| nc | | grep |
<--(TCP)--| socket stdin +---+ stdout |
+------------------+ +-------------+
This example is back to the functionality that (x)inetd would provide.
The idea being that grep* would act on the data that came in the TCP
connection and send the matching lines out the same TCP connection.
*grep is just a hypothetical example here.
> I'm not sure if that is even possible, although you can't rule out
> creative uses of dup2() etc...
~chuckle~
--
Grant. . . .
unix || die
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4013 bytes --]
next prev parent reply other threads:[~2020-03-26 4:11 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-06 22:44 [TUHS] First appearance of named pipes Noel Chiappa
2020-03-07 12:17 ` Paul Ruizendaal
2020-03-07 13:29 ` Clem Cole
2020-03-07 16:39 ` Derek Fawcus
2020-03-08 2:36 ` Rob Pike
2020-03-08 2:47 ` Larry McVoy
2020-03-08 13:07 ` Ralph Corderoy
2020-03-08 13:25 ` arnold
2020-03-08 3:06 ` Dave Horsfall
2020-03-08 7:16 ` arnold
2020-03-08 15:13 ` [TUHS] sockets (was Re: First appearance of named pipes) Derek Fawcus
2020-03-09 23:22 ` Grant Taylor via TUHS
2020-03-09 23:44 ` Larry McVoy
2020-03-23 8:49 ` Peter Pentchev
2020-03-24 9:47 ` Derek Fawcus
2020-03-25 23:25 ` Grant Taylor via TUHS
2020-03-25 23:47 ` Richard Salz
2020-03-26 0:11 ` Grant Taylor via TUHS
2020-03-26 0:18 ` Richard Salz
2020-03-26 1:08 ` Grant Taylor via TUHS
2020-03-26 2:38 ` Dave Horsfall
2020-03-26 3:08 ` Rob Pike
2020-03-26 3:43 ` George Michaelson
2020-03-26 4:11 ` Grant Taylor via TUHS [this message]
2020-03-28 11:12 ` Peter Pentchev
2020-03-28 11:14 ` Peter Pentchev
2020-03-28 16:03 ` Steffen Nurpmeso
2020-03-26 1:20 ` Tony Finch
2020-03-27 10:51 ` Derek Fawcus
2020-03-09 23:22 ` [TUHS] First appearance of named pipes Grant Taylor via TUHS
2020-03-10 7:29 ` arnold
2020-03-11 2:47 ` Grant Taylor via TUHS
2020-03-11 7:02 ` arnold
2020-03-10 13:49 ` Chet Ramey
2020-03-10 20:26 ` Dave Horsfall
2020-03-10 20:37 ` Chet Ramey
2020-03-11 2:51 ` Grant Taylor via TUHS
2020-03-08 23:09 [TUHS] sockets (was Re: First appearance of named pipes) Norman Wilson
2020-03-09 17:09 ` Tony Finch
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=25956003-d4df-36ab-fd89-37c90bf40a13@spamtrap.tnetconsulting.net \
--to=tuhs@minnie.tuhs.org \
--cc=gtaylor@tnetconsulting.net \
/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).