Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > gnu.bash.bug > #16242

Re: Unbuffered pipes: cases to be supported

Path csiph.com!goblin1!goblin.stu.neva.ru!usenet.stanford.edu!not-for-mail
From Ángel <angel@16bits.net>
Newsgroups gnu.bash.bug
Subject Re: Unbuffered pipes: cases to be supported
Date Sat, 25 Apr 2020 17:26:52 +0200
Lines 14
Approved bug-bash@gnu.org
Message-ID <mailman.1218.1587828421.3066.bug-bash@gnu.org> (permalink)
References <878silvimy.fsf@hobgoblin.ariadne.com> <1587828412.1138.2.camel@16bits.net>
NNTP-Posting-Host lists.gnu.org
Mime-Version 1.0
Content-Type text/plain; charset="ISO-8859-15"
Content-Transfer-Encoding quoted-printable
X-Trace usenet.stanford.edu 1587828421 4512 209.51.188.17 (25 Apr 2020 15:27:01 GMT)
X-Complaints-To action@cs.stanford.edu
To bug-bash@gnu.org
Envelope-to bug-bash@gnu.org
In-Reply-To <878silvimy.fsf@hobgoblin.ariadne.com>
Received-SPF pass client-ip=199.195.249.9; envelope-from=angel@16bits.net; helo=mailer.hiddenmail.net
X-detected-operating-system by eggs.gnu.org: First seen = 2020/04/25 11:26:57
X-ACL-Warn Detected OS = Linux 3.11 and newer [fuzzy]
X-Received-From 199.195.249.9
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 <1587828412.1138.2.camel@16bits.net>
X-Mailman-Original-References <878silvimy.fsf@hobgoblin.ariadne.com>
Xref csiph.com gnu.bash.bug:16242

Show key headers only | View raw


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

Best regards


Back to gnu.bash.bug | Previous | Next | Find similar


Thread

Re: Unbuffered pipes:  cases to be supported Ángel <angel@16bits.net> - 2020-04-25 17:26 +0200

csiph-web