Path: utzoo!attcan!utgpu!news-server.csri.toronto.edu!rutgers!cs.utexas.edu!swrinde!emory!mephisto!prism!gt0178a
From: gt0178a@prism.gatech.EDU (BURNS,JIM)
Newsgroups: comp.unix.questions
Subject: Re: How to transfer file descriptors with UNIX domain sockets?
Message-ID: <10981@hydra.gatech.EDU>
Date: 1 Jul 90 19:27:28 GMT
References: <1990Jul01.130157.3627@virtech.uucp>
Organization: Georgia Institute of Technology
Lines: 15

in article <1990Jul01.130157.3627@virtech.uucp>, cpcahil@virtech.uucp (Conor P. Cahill) says:
>>in article <1421@tub.UUCP>, net@tub.UUCP (Oliver Laumann) says:
	[code deleted]
> The system knows because the person, or persons, that added that capability
> to the sockets code ensured that the file descriptor that was passed became
> a valid file descriptor in the process that received it.

I'm sure that it *can* be done - my question is what was it in Oliver
Laumann's code that informed the kernel that what was in the message was a
file descriptor?
-- 
BURNS,JIM
Georgia Institute of Technology, Box 30178, Atlanta Georgia, 30332
uucp:	  ...!{decvax,hplabs,ncar,purdue,rutgers}!gatech!prism!gt0178a
Internet: gt0178a@prism.gatech.edu