Re: kern_control question
Re: kern_control question
- Subject: Re: kern_control question
- From: Josh Graessley <email@hidden>
- Date: Wed, 17 Aug 2005 13:20:00 -0700
They are not the same. But...
You can use the getsockopt in a similar way to ioctl. For kernel
control sockets, the contents of the buffer passed to the socket
option is copied in to the kernel's address space before the option
is passed off to the registered kernel control. In this way, you may
use the getsockopt as read/write. This behavior is new as of 10.4.2.
This change was made at the request of a third party.
-josh
On Aug 17, 2005, at 1:04 PM, Peter Lovell wrote:
Actually they're not quite equivalent. ioctl allows the data area
to be read/write, but socket options are one or the other, not both.
However, I can work around the issue. Thanks for the confirmation.
Regards.....Peter
On Aug 17, 2005, at 2:50 PM, Josh Graessley wrote:
That is correct. You can use socket options instead.
-josh
On Aug 17, 2005, at 11:43 AM, Peter Lovell wrote:
Hi all,
this is a question for which I think I have the answer but I'm
posing it just to make sure I haven't overlooked anything.
It seems to me that kern_control sockets do not support user-
defined ioctls, just CTLIOCGCOUNT and CTLIOCGINFO. Is this correct?
Thanks.....Peter
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-kernel mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40apple.com
This email sent to email@hidden
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
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