Patch to pass file descriptors

David Euresti davie@MIT.EDU
Mon Jul 1 14:42:00 GMT 2002

Oops. I posted this to the wrong list.  Here it is in context.

        There's the option of keeping full BSD semantics if the cygserver
is running.  I like that.  I can require users to run the cygserver.  I
don't mind.
        Unfortunately the whole has been refactored so I'll have to
regenerate my patch.
        The question is, can you incorporate my code and then you guys
deal with the case when the cygserver isn't running?  I don't really have
a use for a non cygserver solution because my program depends on full BSD
semantics.  Such as closing the handle after sending it, or exiting the
process after sending it.  I don't see how to solve this second problem
without the cygserver.
        I'm sure other people will want full BSD semantics also so why not
allow them to have it if the cygserver is running.

By the way, I thought about how to solve the problem of the program
closing the handle after sending it.  Assuming that you'll spawn a thread
with your shared memory stuff.  You can dup the handle in that thread.
Then the sender can do whatever it wants with it's copy (Close it), and
when the receiver has it, it can tell the sender to release it.
Unfortunately this won't help the situation where the sender process
exits before the receiver receives.

        Also should this discussion be moved to cygwin-developers?


More information about the Cygwin-patches mailing list