Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <001e01c280be$2ea08ad0$2a519085@yano01>
From: "Takashi Yano" <yano AT crl DOT hitachi DOT co DOT jp>
To: <cygwin AT cygwin DOT com>
Subject: 1.3.13-2 & 1.3.14-1 problem on read() from dgram socket
Date: Thu, 31 Oct 2002 18:16:23 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-2022-jp"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106

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.

Thank you.

--
Takashi Yano

--
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/