Re: shutdown( socket, SHUT_WR ) - unexpected behaviour

[Larry Hall <cygwin-lh at cygwin dot com>]

At 10:19 PM 5/3/2004, you wrote:

>> I've tried your application and I'm not able to reproduce your problem.
>> The shutdown call does not influence sending the buffered data apparently.
>
>Thanks for info.
>
>> I've tested with Cygwin 1.5.9 and with a recent snapshot on XP SP1.
>> What's your system?
>
>Cygwin 1.5.9, Win2kSP2.  I made additional test using winsock directly
>and got the same buggy result.  So it doesn't look like bug in cygwin,
>but rather in windows or some 3rd party app that is messing with the
>sockets (e.g. NIS).  I found similar bugreport in MS KB298871, but it's
>marked as WinCE only:
>
>http://support.microsoft.com/default.aspx?scid=kb;en-us;298871
>
>"If an application calls shutdown() to disable only sending from the
>socket, later attempts to read data sent to that socket will result in
>only portions of the data being received."
>
>
>Can somebody with Win2k box compile and run prog from my previous mail?
>I would like to know if it behaves incorrectly only on my system, or on
>Win2k in general:


I don't know if this answers the question or not but it works fine for
me on W2K SP3 (Cygwin 1.5.9 yada, yada)...



--
Larry Hall                              http://www.rfk.com
RFK Partners, Inc.                      (508) 893-9779 - RFK Office
838 Washington Street                   (508) 893-9889 - FAX
Holliston, MA 01746                     


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/