From owner-freebsd-stable Tue Dec 11 6: 6:32 2001 Delivered-To: freebsd-stable@freebsd.org Received: from lurza.secnetix.de (lurza.secnetix.de [212.66.1.130]) by hub.freebsd.org (Postfix) with ESMTP id 19CA337B419 for ; Tue, 11 Dec 2001 06:06:29 -0800 (PST) Received: (from olli@localhost) by lurza.secnetix.de (8.11.6/8.11.6) id fBBE6UO91751; Tue, 11 Dec 2001 15:06:30 +0100 (CET) (envelope-from oliver.fromme@secnetix.de) Date: Tue, 11 Dec 2001 15:06:30 +0100 (CET) Message-Id: <200112111406.fBBE6UO91751@lurza.secnetix.de> From: Oliver Fromme To: freebsd-stable@FreeBSD.ORG Reply-To: freebsd-stable@FreeBSD.ORG Subject: Re: read(2) on BLOCKED socket In-Reply-To: <20011211142317.A1245@bspu.secna.ru> X-Newsgroups: list.freebsd-stable User-Agent: tin/1.5.4-20000523 ("1959") (UNIX) (FreeBSD/4.4-RELEASE (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit 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 mitrohin a.s. wrote: > Why socket blocked read(2) return big data by portions? Because POSIX and SUSv2 say so: The value returned may be less than if the number of bytes left in the file is less than , if the read() request was interrupted by a signal, or if the file is a pipe or FIFO or special file and has fewer than bytes immediately available for reading. Regards Oliver -- Oliver Fromme, secnetix GmbH & Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "All that we see or seem is just a dream within a dream" (E. A. Poe) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message