From owner-freebsd-questions@FreeBSD.ORG Thu Dec 20 17:51:29 2007 Return-Path: Delivered-To: questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A669616A418 for ; Thu, 20 Dec 2007 17:51:29 +0000 (UTC) (envelope-from mi+mill@aldan.algebra.com) Received: from mail7.sea5.speakeasy.net (mail7.sea5.speakeasy.net [69.17.117.9]) by mx1.freebsd.org (Postfix) with ESMTP id 7A9F813C442 for ; Thu, 20 Dec 2007 17:51:29 +0000 (UTC) (envelope-from mi+mill@aldan.algebra.com) Received: (qmail 31772 invoked from network); 20 Dec 2007 17:51:29 -0000 Received: from aldan.algebra.com (HELO aldan-mlp) ([216.254.65.224]) (envelope-sender ) by mail7.sea5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 20 Dec 2007 17:51:28 -0000 From: Mikhail Teterin To: Erik Osterholm Date: Thu, 20 Dec 2007 12:51:26 -0500 User-Agent: KMail/1.7.1 References: <200712192322.lBJNMfps053071@aldan.algebra.com> <200712201102.59565@aldan> <20071220165807.GA34089@aleph.cepheid.org> In-Reply-To: <20071220165807.GA34089@aleph.cepheid.org> Organization: Virtual Estates, Inc. MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-u" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200712201251.27067.mi+mill@aldan.algebra.com> Cc: questions@freebsd.org Subject: Re: tail does not exit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Dec 2007 17:51:29 -0000 =DE=C5=D4=D7=C5=D2 20 =C7=D2=D5=C4=C5=CE=D8 2007 11:58 =C4=CF, Erik Osterho= lm =F7=C9 =CE=C1=D0=C9=D3=C1=CC=C9: > Ah, I see. =9AWith very, very long lines, tail doesn't send the output > all at once. The cutoff seems to be 65536 bytes on my system. They don't even have to be very very long -- unless in an artificial exampl= e,=20 such as the one I posted. Normal-width text files can also trigger=20 inconsistent behavior in some real-life scenario, where awk actually does=20 some real processing of its input for a while. The awk script may decide to= =20 quit after processing the first 1000 (normal-length) lines, for example...= =20 The behavior of the program will then be different depending on whether the= =20 average line-length is above, at, or below 65.536 characters. Maybe, it is awk's fault -- it should not be read-ing more than one line at= a=20 time, because the script may cause it to ignore some of the read data. Using line-buffering or some such? -mi