Re: all connect(2) calls are failures?
Re: all connect(2) calls are failures?
- Subject: Re: all connect(2) calls are failures?
- From: Josh Graessley <email@hidden>
- Date: Fri, 18 May 2007 11:30:58 +0200
Most apps use non-blocking connects. These will start the connect and
return immediately with an error indicating that the operation is in
progress. This isn't a failure, it's just part of the API.
-josh
(from afar)
On May 17, 2007, at 4:13 AM, Todd Heberlein <email@hidden>
wrote:
I am looking through Apple's BSM audit logs (Mac OS X 10.4.9 on a
G5), and all records for the connect(2) system call to an IP address
are reported as failures. There are no examples of successful
connection requests even though I know they took place.
A typical audit record is:
header,88,1,connect(2),0,Tue May 15 09:44:38 2007, + 731 msec
argument,1,0x10,fd
socket-inet,2,80,17.250.248.77
subject,heberlei,heberlei,staff,heberlei,staff,
384,196,50331650,0.0.0.0
return,failure : Operation now in progress,4294967295
trailer,88
The audit flags are set for "all".
Is this a bug in Apple's kernel (i.e., inadvertently reporting a
successful system call as a failure), or did Apple choose *not* to
report successful network connections?
Thanks,
Todd
_______________________________________________
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
_______________________________________________
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