Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!bellcore!decvax!decwrl!pyramid!pesnta!wjvax!brett
From: brett@wjvax.UUCP
Newsgroups: net.unix-wizards
Subject: Re: UNIX domain sockets ?
Message-ID: <700@wjvax.wjvax.UUCP>
Date: Mon, 19-May-86 12:18:49 EDT
Article-I.D.: wjvax.700
Posted: Mon May 19 12:18:49 1986
Date-Received: Fri, 23-May-86 07:15:56 EDT
References: <596@brl-smoke.ARPA> <248@rtech.UUCP> <6928@mordor.ARPA>
Reply-To: brett@wjvax.UUCP (Brett Galloway)
Organization: Watkins-Johnson Co., San Jose, Calif.
Lines: 18

In article <6928@mordor.ARPA> jdb@mordor.UUCP (John Bruner) writes:
>Aside from issues of speed, UNIX domain sockets provide a capability ...
>to pass file descriptors between processes using UNIX domain datagrams.

I am curious -- how?  In addition, I have a general question.  It looks to
me like the name to which a UNIX domain socket may be bound is limited to
13 or fewer characters (at least in our implementation - VAX 750, Mt Xinu
4.2 BSD) in the struct sockaddr structure.  UNIX domain socket names
are located in the filesystem, and this 13 character name length limit
seems severely to restrict where in the filesystem a socket name may reside.
How do other people manage this restriction?  Is there such a restriction?  If
so, where do people typically put socket names -- in /etc?

Please respond by E-Mail; I will summarize.  Thanks (in advance)

-------------
Brett Galloway
{pesnta,twg,ios,qubix,turtlevax,tymix,vecpyr,certes,isi}!wjvax!brett