Re: Notification of fork()
Re: Notification of fork()
- Subject: Re: Notification of fork()
- From: Michael Smith <email@hidden>
- Date: Tue, 26 Dec 2006 12:12:43 -0800
On Dec 26, 2006, at 11:50 AM, Curtis Jones wrote:
So, even if the incoming connection does not have a pid associated
with it (at the time that I need to know the pid), I do know the
associated local port, and I can look at the existing listeners and
find the one that corresponds, and I know the pid that created the
listener (even if it is not the one that is calling accept). So, in
some cases I'll have the correct pid/path, and in other cases I'll
have just one value or neither.
I tried to parse your original description, but was unable to deduce
what you're actually trying to do.
Are you attempting to determine the identity of the originator of the
incoming connection, or the party that will ultimately call accept(2)?
Is there any reason why you have to know early, rather than waiting
until the connection is accepted before determining whether or not to
block it?
= Mike
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-kernel mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden