Path: csiph.com!goblin1!goblin.stu.neva.ru!usenet.stanford.edu!not-for-mail
From: worley@alum.mit.edu (Dale R. Worley)
Newsgroups: gnu.bash.bug
Subject: Re: Unbuffered pipes:  cases to be supported
Date: Mon, 27 Apr 2020 21:54:02 -0400
Lines: 17
Approved: bug-bash@gnu.org
Message-ID: <mailman.1444.1588038855.3066.bug-bash@gnu.org>
References: <1587828412.1138.2.camel@16bits.net> (angel@16bits.net) <87sggofk91.fsf@hobgoblin.ariadne.com>
NNTP-Posting-Host: lists.gnu.org
X-Trace: usenet.stanford.edu 1588038855 26030 209.51.188.17 (28 Apr 2020 01:54:15 GMT)
X-Complaints-To: action@cs.stanford.edu
Cc: bug-bash@gnu.org
To: =?utf-8?Q?=C3=81ngel?= <angel@16bits.net>
Envelope-to: bug-bash@gnu.org
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcastmailservice.net; s=20180828_2048; t=1588038846; bh=ve1xKzCdMbZP+s2WwQ+Vp8jplrnIeOJtXr86AsW7TBs=; h=Received:Received:Received:Received:From:To:Subject:Date: Message-ID; b=lfcTLz5kkTtzvYqQwKvTb8BERqNRNvwAUfmHK0CUuoO+xjle2G8ZpZqqDkqzKllVb 9rR5bY/vAFHHzGjHvU0I35eSYkYm/LjelYgaN/5dOggvXqOL3qgg6kiU4ZhQOEpmWn q6pjGfQPb6qZnyL+sDN/2WEV8PfgNa+IdXYyv1JGAg8spnrlXEgOzDVgJNZGlDvGa6 tsWtJ71Eod12qyCOoGcz2AgB3o4lkP7tN/UCcqV/Z9RFA5wP27ojNbmtODmqRNbi3s pjWsQ3XJF51bLlQJhIJxeiNUJI4R7lg7uZ/fO3ZSAq/ehYImP5JSAUzKt0X7b35fRz RGFnUmKItDLHw==
X-Xfinity-VMeta: sc=0.00;st=legit
X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f
In-Reply-To: <1587828412.1138.2.camel@16bits.net> (angel@16bits.net)
Received-SPF: softfail client-ip=2001:558:fe21:29:69:252:207:41; envelope-from=worley@alum.mit.edu; helo=resqmta-ch2-09v.sys.comcast.net
X-detected-operating-system: by eggs.gnu.org: First seen = 2020/04/27 21:54:06
X-ACL-Warn: Detected OS   = ???
X-Received-From: 2001:558:fe21:29:69:252:207:41
X-BeenThere: bug-bash@gnu.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Bug reports for the GNU Bourne Again SHell <bug-bash.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/bug-bash>, <mailto:bug-bash-request@gnu.org?subject=unsubscribe>
List-Archive: <https://lists.gnu.org/archive/html/bug-bash>
List-Post: <mailto:bug-bash@gnu.org>
List-Help: <mailto:bug-bash-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/bug-bash>, <mailto:bug-bash-request@gnu.org?subject=subscribe>
X-Mailman-Original-Message-ID: <87sggofk91.fsf@hobgoblin.ariadne.com>
Xref: csiph.com gnu.bash.bug:16251

Angel <angel@16bits.net> writes:
> On 2020-04-23 at 20:20 -0400, Dale R. Worley wrote:
>> The cases I've found where bash allocates a pipe, and thus an unbuffered
>> pipe may be wanted, are:
>
> What are you trying to solve? How do you expect those "Unbuffered pipes"
> to be implemented?
> I don't think there is any buffering going on in the pipes itself. The
> problem is likely to be at the program *writing* to the pipe. Which is
> out of the scope of bash itself. You may want to run them through stdbuf

It's true that pipes themselves don't have any buffering themselves (of
this sort).  But if you go back to my original message, it explains the
limitations of stdbuf that I'm trying to get rid of.

Dale