From owner-freebsd-stable Tue Dec 11 0:59:13 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mirage.secna.ru (mirage.secna.ru [212.192.0.20]) by hub.freebsd.org (Postfix) with ESMTP id 32D0E37B416 for ; Tue, 11 Dec 2001 00:53:28 -0800 (PST) Received: from bspu.secna.ru (root@gw-bspu-astu-2M.bspu.secna.ru [212.192.2.1]) by mirage.secna.ru (8.9.1/8.9.1-secna) with ESMTP id OAA90144 for ; Tue, 11 Dec 2001 14:27:08 +0600 (NOVT) Received: (from root@localhost) by bspu.secna.ru (8.11.6/8.11.6) id fBB8NIv14062 for freebsd-stable@FreeBSD.ORG; Tue, 11 Dec 2001 14:23:18 +0600 (NS) Date: Tue, 11 Dec 2001 14:23:17 +0600 From: "mitrohin a.s." To: freebsd-stable@FreeBSD.ORG Subject: read(2) on BLOCKED socket Message-ID: <20011211142317.A1245@bspu.secna.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.20i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG ehlo. Why socket blocked read(2) return big data by portions? imho, block process while reading full buffer more correctly. /swp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message