From: Gerald Waugh <gwaugh@frontstreetnetworks.com>
To: linux-c-programming@vger.kernel.org
Subject: child processes
Date: Mon, 22 Apr 2002 09:39:01 -0400 [thread overview]
Message-ID: <02042209461600.15975@linux1.fastinc.com> (raw)
I am not doing a good job of explaining my requirements, but I am looking for
ideas...
I have an assignment to do an applicaiton that must communicate on
three different TCP ports...
I was wondering if I could run a daemon that would create three child
processes, one for each of the tcp ports?
Then have the daemon run any time there was communications activity on any of
the ports
The daemon must translate the data coming in any one of the ports to a protocol
acceptable to the port the data is to be sent to.
Any ideas?.
--
Gerald Waugh
http://www.frontstreetnetworks.com
Front Street Networks LLC - 203-785-0699
229 Front Street, Ste. #C, New Haven CT, 06513-3203
next reply other threads:[~2002-04-22 13:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-22 13:39 Gerald Waugh [this message]
2002-04-22 18:15 ` child processes Ajay Dudani
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=02042209461600.15975@linux1.fastinc.com \
--to=gwaugh@frontstreetnetworks.com \
--cc=linux-c-programming@vger.kernel.org \
/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).