NetNews Usenet Archive 1992 #26/NN_1992_26.iso/spool/comp/os/mswindo/programm/win32/1909

Text File | 1992-11-10 | 1.9 KB | 60 lines

Newsgroups: comp.os.ms-windows.programmer.win32
Path: sparky!uunet!utcsri!torn!maccs!beame
From: [e-mail] (Carl Beame)
Subject: Re: DuplicateHandle -- passing handles to other processes
Message-ID: <[e-mail]>
Organization: Department of Computer Science, McMaster University
References: <[e-mail]> <[e-mail]> <[e-mail]>
Date: Wed, 11 Nov 1992 01:28:54 GMT
Lines: 49

In article <[e-mail]> [e-mail] (Dave Kolb) writes:

Stuff delete
>
>My questions/suggestions are two:
>
>- Does the pipe that CreateFile is opening already exist?  If not you
>  don't have a valid handle to pass.

    The pipe named in the CreateFile already exists, and communication has
already taken place between this process and the pipe creator.

>
>- You need to set the inherit flag in the lpsa security attributes
>  data structure when creating the remote handle.

I do actually call the CreateFile with the following security attributes:

SECURITY_ATTRIBUTES sa;

    sa.nLength=sizeof(sa);
    sa.bInheritHandle=TRUE;
    sa.lpSecurityDescriptor=NULL;
>
>P.S. How does the created process open the local pipe if the remote# is part of
>the pipe name and that's what you're trying to pass it?  And why pass it if it
>already knows it?  Or why not just have the created process open up the remote pipe?

    I am passing the name of the local pipe in the command line to the
remote process so it can connect back to the creator process to receive
the value of the newly created handle.

>
>I guess this is a contrived fragment???

    Not really, I just changed the name of the pipes used.

>
>Let us know...
>
>--
>Dave Kolb                     Opinions are mine not SAS'
>SAS Institute, Inc.           EMAIL:      [e-mail]
>SAS Campus Drive - J206       Phone:      [phone] x6827
>Cary, NC  27513-2414 USA      FAX:        [phone]
>

- Carl Beame