bug-hurd
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bugs #12434] Unix-domain (local) sockets do not support getsockname() o


From: Marcus Brinkmann
Subject: [bugs #12434] Unix-domain (local) sockets do not support getsockname() or getpeername()
Date: Wed, 23 Mar 2005 21:23:34 +0000
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20050105 Galeon/1.3.19 (Debian package 1.3.19-4)

Update of bugs #12434 (project hurd):

         Originator Name:                         => deven@ties.org         

    _______________________________________________________

Follow-up Comment #1:

Calling getsockname() on a Unix Domain Socket does not seem to be widely
supported.  I found the following two references:

Cygwin:
http://www.cygwin.com/ml/cygwin-patches/2002-q4/msg00064.html
>       (fhandler_socket::getsockname): Call ::getsockname() even for UNIX
>       domain sockets as an error check.

Note the formula: "as an error check".

AIX:
http://publib16.boulder.ibm.com/pseries/en_US/libs/commtrf2/getsockname.htm
Note:
The getsockname subroutine does not perform operations on UNIX domain
sockets.

FreeBSD:
http://www.gsp.com/cgi-bin/man.cgi?section=2&topic=getsockname
BUGS
    Names bound to sockets in the UNIX domain are inaccessible; getsockname
returns a zero length name.


There is a fundamental issue with supporting it: The filename used in the
filesystem space in the creator may not be the same as one in the task
querying it.

So, it is questionable what the semantics of this call on Unix Domain Sockets
should be.


    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?func=detailitem&item_id=12434>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/





reply via email to

[Prev in Thread] Current Thread [Next in Thread]