From: Steve G <linux_4ever@yahoo.com>
To: netdev@oss.sgi.com
Subject: Unaccepted Connections
Date: Mon, 7 Jul 2003 07:03:43 -0700 (PDT) [thread overview]
Message-ID: <20030707140343.14852.qmail@web9602.mail.yahoo.com> (raw)
Hello,
I have a user space programming question and need some
ideas from networking gurus. I am working on a well known
inet daemon that listens for tcp connections and passes the
descriptor returned by listen() to a child program to
handle in the tcp/wait mode.
It turns out that many child programs error during their
startup and exit without accepting the connection
(linuxconf is one of them). The daemon that listens sees
the descriptor as readable and starts a new child...which
dies. This can loop forever.
The questions are:
1) How can a parent process reliably determine that its
child has indeed accepted the connection? (ptrace is not a
good solution.)
2) Is it possible to tell anything about a connection that
has returned from listen but not yet accepted? For instance
the source IP address? Or checksum? Can recvfrom PEEK into
the packet?
Thanks,
Steve Grubb
__________________________________
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com
reply other threads:[~2003-07-07 14:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20030707140343.14852.qmail@web9602.mail.yahoo.com \
--to=linux_4ever@yahoo.com \
--cc=netdev@oss.sgi.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 NNTP newsgroup(s).