Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Thu, 31 Oct 2002 13:48:16 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: 1.3.13-2 & 1.3.14-1 problem on read() from dgram socket Message-ID: <20021031184816.GF18735@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <001e01c280be$2ea08ad0$2a519085 AT yano01> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <001e01c280be$2ea08ad0$2a519085@yano01> User-Agent: Mutt/1.5.1i On Thu, Oct 31, 2002 at 06:16:23PM +0900, Takashi Yano wrote: >Hello, everyone. > >I'd like to report bug of latest release of cygwin. > >I found that read() from dgram socket fails on cygwin 1.3.13-2 or 1.3.14-1 >under Windows 2000 or Windows XP. > >Cygwin 1.3.12-4 does not have this problem. >Also, this problem does not apear under Windows 98. > >Due to this problem, inetd of inetutils-1.3.2-19 get into full load >after receiving dgram "discard" request on udp port 9. >Build-in "discard" daemon of inetd calls read() instead of recv() >to sink data from dgram socket in discard_dg(), but the read() fails. >Then select() returns repeatedly every time after read() fails. > >I hope this problem will be resolved in next release. If you provide a simple test case, I'm sure that it probably will be resolved. Also, check out: http://cygwin.com/bugs.html . cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/