Date: Wed, 29 Apr 1998 00:13:25 -0700 (PDT) From: archer@lucky.net To: freebsd-gnats-submit@FreeBSD.ORG Subject: gnu/6448: grep doesn't flush its output. Message-ID: <199804290713.AAA10866@hub.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 6448 >Category: gnu >Synopsis: grep doesn't flush its output. >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: change-request >Submitter-Id: current-users >Arrival-Date: Wed Apr 29 00:20:01 PDT 1998 >Last-Modified: >Originator: Alexander Litvin >Organization: Lucky Net Ltd. >Release: 3.0-CURRENT >Environment: FreeBSD grape.carrier.kiev.ua 3.0-CURRENT FreeBSD 3.0-CURRENT #72: Tue Apr 28 14 :18:19 EEST 1998 archer@grape.carrier.kiev.ua:/usr/src/sys/compile/GRAPE i386 >Description: grep uses fwrite() to write its output. Without flushing stdin it means that the following: $ tail -f foo | grep bar | grep zu won't work. >How-To-Repeat: Run 'grep foo | cat'. Until 'grep' finds EOF, nothing will be read (and written to the screen) by 'cat'. >Fix: In prline(), gnu/usr.bin/grep/grep.c, stdout should be flushed after fwrite(). >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199804290713.AAA10866>