Home > Archive > Unix Programming > September 2005 > accept(2) doesn't populate sun_path?
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
accept(2) doesn't populate sun_path?
|
|
| Michael B Allen 2005-09-21, 9:57 pm |
| I've noticed accept(2) doesn't populate the sun_path member of struct
sockaddr_un. The len returned is 2 for sin_family but there's no path. Is
this universal behavoir for UNIX sockets? Right now I'm using Linux 2.6.
Thanks,
Mike
| |
| Barry Margolin 2005-09-21, 9:57 pm |
| In article <pan.2005.09.22.00.00.54.967806@ioplex.com>,
Michael B Allen <mba2000@ioplex.com> wrote:
> I've noticed accept(2) doesn't populate the sun_path member of struct
> sockaddr_un. The len returned is 2 for sin_family but there's no path. Is
> this universal behavoir for UNIX sockets? Right now I'm using Linux 2.6.
With Unix domain sockets there is no remote address, so what should it
be populated with?
--
Barry Margolin, barmar@alum.mit.edu
Arlington, MA
*** PLEASE post questions in newsgroups, not directly to me ***
| |
| Michael B Allen 2005-09-21, 9:57 pm |
| On Wed, 21 Sep 2005 21:07:24 -0400, Barry Margolin wrote:
>
> With Unix domain sockets there is no remote address, so what should it
> be populated with?
Duh, that makes sense. Nevermind.
Thanks,
Mike
|
|
|
|
|