The second patch in this series enables opening a FIFO with O_RDWR
access. The underlying Windows named pipe is creted with duplex
access, and its handle is made the I/O handle of the first client.
While testing this, I had some mysterious crashes, which are fixed by
the first patch.
I tested th
Hi Ken,
On Mar 25 23:06, Ken Brown wrote:
> The second patch in this series enables opening a FIFO with O_RDWR
> access. The underlying Windows named pipe is creted with duplex
> access, and its handle is made the I/O handle of the first client.
>
> While testing this, I had some mysterious cras
Hi Corinna,
On 3/26/2019 4:36 AM, Corinna Vinschen wrote:
> Hi Ken,
>
> On Mar 25 23:06, Ken Brown wrote:
>> The second patch in this series enables opening a FIFO with O_RDWR
>> access. The underlying Windows named pipe is creted with duplex
>> access, and its handle is made the I/O handle of t
On Mar 26 17:24, Ken Brown wrote:
> Hi Corinna,
>
> On 3/26/2019 4:36 AM, Corinna Vinschen wrote:
> > Hi Ken,
> >
> > On Mar 25 23:06, Ken Brown wrote:
> >> The second patch in this series enables opening a FIFO with O_RDWR
> >> access. The underlying Windows named pipe is creted with duplex
> >
On Mar 26 20:01, Corinna Vinschen wrote:
> On Mar 26 17:24, Ken Brown wrote:
> > Hi Corinna,
> >
> > On 3/26/2019 4:36 AM, Corinna Vinschen wrote:
> > > Hi Ken,
> > >
> > > On Mar 25 23:06, Ken Brown wrote:
> > >> The second patch in this series enables opening a FIFO with O_RDWR
> > >> access.
Corinna Vinschen writes:
> Done. I also pushed out new dev snapshots.
No good deed goes unpunished…
Whith the 20190327 snapshot our main data processing application is
broken. It looks like it should almost work, it doesn't crash or
anything, but the pipe that delivers a script+data into gnuplo
On Mar 28 19:01, Achim Gratz wrote:
> Corinna Vinschen writes:
> > Done. I also pushed out new dev snapshots.
>
> No good deed goes unpunished…
>
> Whith the 20190327 snapshot our main data processing application is
> broken. It looks like it should almost work, it doesn't crash or
> anything,
On Mar 28 21:13, Corinna Vinschen wrote:
> On Mar 28 19:01, Achim Gratz wrote:
> > Corinna Vinschen writes:
> > > Done. I also pushed out new dev snapshots.
> >
> > No good deed goes unpunished…
> >
> > Whith the 20190327 snapshot our main data processing application is
> > broken. It looks lik
On 3/28/2019 4:13 PM, Corinna Vinschen wrote:
> On Mar 28 19:01, Achim Gratz wrote:
>> Corinna Vinschen writes:
>>> Done. I also pushed out new dev snapshots.
>>
>> No good deed goes unpunished…
>>
>> Whith the 20190327 snapshot our main data processing application is
>> broken. It looks like it
Ken Brown writes:
>> I'm pretty sure Ken would be happy about an STC.
>
> Yes, please. Barring that, is there any chance I could see the relevant
> code,
> or at least enough of it so that I can see how FIFOs are being used?
Well, I'm trying -- but got nothing so far. As the individual FIFO se
On 3/29/2019 3:17 AM, Achim Gratz wrote:
> Ken Brown writes:
>>> I'm pretty sure Ken would be happy about an STC.
>>
>> Yes, please. Barring that, is there any chance I could see the relevant
>> code,
>> or at least enough of it so that I can see how FIFOs are being used?
>
> Well, I'm trying --
Ken Brown writes:
> I found a bug in my fhandler_fifo::raw_write code that could explain the
> problem. The call to NtWriteFile in that function always returns immediately
> because the Windows named pipe underlying the FIFO is non-blocking. If it
> can't
> write because the pipe buffer is fu
Achim Gratz writes:
> OK, a bit more info: The whole thing runs from a perl script (actually a
> module) that opens pipes to gnuplot and ghostscript. This code is
> _really_ old and has seen a lot of Cygwin releases, so it has options to
> either use temporary files, named pipes aka FIFO or direct
On 4/3/2019 8:33 AM, Achim Gratz wrote:
> Achim Gratz writes:
>> OK, a bit more info: The whole thing runs from a perl script (actually a
>> module) that opens pipes to gnuplot and ghostscript. This code is
>> _really_ old and has seen a lot of Cygwin releases, so it has options to
>> either use t
On 3/25/2019 7:06 PM, Ken Brown wrote:
> The second patch in this series enables opening a FIFO with O_RDWR
> access. The underlying Windows named pipe is created with duplex
> access, and its handle is made the I/O handle of the first client.
>
> I tested the patch in two ways.
>
> First,
[...
On 4/29/2019 2:29 PM, Ken Brown wrote:
> On 3/25/2019 7:06 PM, Ken Brown wrote:
>> The second patch in this series enables opening a FIFO with O_RDWR
>> access. The underlying Windows named pipe is created with duplex
>> access, and its handle is made the I/O handle of the first client.
>>
>> I te
On Apr 29 18:42, Ken Brown wrote:
> On 4/29/2019 2:29 PM, Ken Brown wrote:
> > On 3/25/2019 7:06 PM, Ken Brown wrote:
> >> The second patch in this series enables opening a FIFO with O_RDWR
> >> access. The underlying Windows named pipe is created with duplex
> >> access, and its handle is made th
On 4/29/2019 3:06 PM, Corinna Vinschen wrote:
> On Apr 29 18:42, Ken Brown wrote:
>> Actually, the answer might be obvious. Looking at MSDN, it now seems
>> clear to me that you can't do I/O on the server side of a pipe until
>> the pipe connects to a client. So I'll have to rethink how to deal
>
18 matches
Mail list logo
