From owner-freebsd-hackers Tue Jun 20 16:55:48 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from stox.sa.enteract.com (stox.sa.enteract.com [207.229.132.161]) by hub.freebsd.org (Postfix) with ESMTP id AA2AB37B59F for ; Tue, 20 Jun 2000 16:55:44 -0700 (PDT) (envelope-from stox@stox.sa.enteract.com) Received: (from stox@localhost) by stox.sa.enteract.com (8.9.3/8.9.3) id SAA01097; Tue, 20 Jun 2000 18:55:36 -0500 (CDT) (envelope-from stox) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20000620211553.31841.qmail@hotmail.com> Date: Tue, 20 Jun 2000 18:55:36 -0500 (CDT) From: "Kenneth P. Stox" To: gerald stoller Subject: RE: Korn shell STDOUT Cc: freebsd-hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 20-Jun-00 gerald stoller wrote: > I am trying to learn how the (Korn) shell is organized, so I put some > printf statements in many places. They give a lot of output on STDOUT , > so in order to be able to read it, I pipe it to a tee command which stores > the output. I have found that the output pauses when the file has 16384 > (or thereabouts) bytes in it, sometimes it goes to 32768 (or thereabouts) > bytes in it, and a couple of times it has even gone up to 65536 (or > thereabouts) bytes. This behavior makes me think of buffered output, but > (with some checking via long files) neither pipe nor tee have buffered > output, and so I have been told by a Bell Labber. Anybody know how I can > easily change the > STDOUT to be unbuffered? You might want to write to stderr which, if memory serves correct, is un-buffered. ---------------------------------- E-Mail: Kenneth P. Stox Date: 20-Jun-00 Time: 18:54:17 ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message