I have a sense that if I was clever enough, I'd be able to see the
magical form of using "exec" that would cause bash to create a pipe-pair
of fd's (like pipe(2) does), with the two fd's accessible as, e.g., fd
10 and 11 of bash. If you did a few of these, you could then plumb
together processes
Date:Wed, 23 Sep 2020 23:18:36 -0700
From:Vito Caputo
Message-ID: <20200924061836.4cu5ttjzdn7rv...@shells.gnugeneration.com>
| In my example, the aggregator can trivially read the separate records
| at the write boundaries from each of the connected packetized
On Thu, Sep 24, 2020 at 12:48:14PM +0700, Robert Elz wrote:
> Date:Wed, 23 Sep 2020 21:47:10 -0700
> From:Vito Caputo
> Message-ID: <20200924044710.xpltp22bpxoxi...@shells.gnugeneration.com>
>
>
> | It's useful if you're doing something like say, aggregating data
Date:Wed, 23 Sep 2020 21:47:10 -0700
From:Vito Caputo
Message-ID: <20200924044710.xpltp22bpxoxi...@shells.gnugeneration.com>
| It's useful if you're doing something like say, aggregating data from
| multiple piped sources into a single bytestream. With the
On Wed, Sep 23, 2020 at 11:53:10PM -0400, Lawrence Velázquez wrote:
> > On Sep 23, 2020, at 11:41 PM, Vito Caputo wrote:
> >
> > On Wed, Sep 23, 2020 at 09:12:40AM -0400, Chet Ramey wrote:
> >> On 9/22/20 11:23 PM, Vito Caputo wrote:
> >>> Hello list,
> >>>
> >>> Is there any chance we could
> On Sep 23, 2020, at 11:41 PM, Vito Caputo wrote:
>
> On Wed, Sep 23, 2020 at 09:12:40AM -0400, Chet Ramey wrote:
>> On 9/22/20 11:23 PM, Vito Caputo wrote:
>>> Hello list,
>>>
>>> Is there any chance we could get a | modifier for enabling O_DIRECT on the
>>> created pipe? "Packet" style
On Wed, Sep 23, 2020 at 09:12:40AM -0400, Chet Ramey wrote:
> On 9/22/20 11:23 PM, Vito Caputo wrote:
> > Hello list,
> >
> > Is there any chance we could get a | modifier for enabling O_DIRECT on the
> > created pipe? "Packet" style pipes have some interesting and potentially
> > useful
On 9/22/20 11:23 PM, Vito Caputo wrote:
> Hello list,
>
> Is there any chance we could get a | modifier for enabling O_DIRECT on the
> created pipe? "Packet" style pipes have some interesting and potentially
> useful properties, it would be nice if bash made them more accessible.
Is there a
Hello list,
Is there any chance we could get a | modifier for enabling O_DIRECT on the
created pipe? "Packet" style pipes have some interesting and potentially
useful properties, it would be nice if bash made them more accessible.
pipe(2) O_DIRECT excerpt:
O_DIRECT (since Linux 3.4)
