This is the mail archive of the cygwin-patches@cygwin.com mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Why no shutdown? (was: Re: SSH -R problem)


On Wed, May 01, 2002 at 10:34:47AM +0100, Max Bowsher wrote:
> On cygwin-patches@, Pierre A. Humblet wrote:
> > >So an ideal fix would detect "end of life" situations. Here is a brain
> > >storming idea: on a Cygwin close(), do a shutdown(.,2), free the Cygwin
> > Oops, absolutely no shutdown().
> >
> > Pierre
> 
> Why no shutdown?

shutdown() disables the socket, not the socket handle.  The result
is that parent as well as child processes using dup'd sockets are
influenced by that.  close() OTOH just wants to disable only this
very socket handle of the calling process.

Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Developer                                mailto:cygwin@cygwin.com
Red Hat, Inc.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]