On Sat, 26 Aug 2023 14:08:34 +
"Lavrentiev, Anton (NIH/NLM/NCBI) [C]" wrote:
> IMO you're triggering an undefined (or not well-defined) behavior, because of
> the murky status
> of the byte count of 0. It may work now, but it may not work in the future...
>
> RETURN VALUE
>On succes
On 2023-08-26 11:44, Martin Wege via Cygwin wrote:
On Fri, Aug 25, 2023 at 2:19 PM Corinna Vinschen via Cygwin
wrote:
On Aug 23 01:05, Roland Mainz via Cygwin wrote:
Note that Cygwin does not interpret the file |myfifo.fifo| as FIFO,
instead it comes back as a symlink "myfifo.fifo -> ':\0:c4:
On 2023-08-26 11:40, Martin Wege via Cygwin wrote:
On Sat, Aug 26, 2023 at 4:16 PM Corinna Vinschen via Cygwin
wrote:
On Aug 26 13:26, Cedric Blancher via Cygwin wrote:
On Fri, 25 Aug 2023 at 14:26, Corinna Vinschen via Cygwin
wrote:
On Aug 25 14:18, Corinna Vinschen via Cygwin wrote:
On
On Thu, Aug 24, 2023 at 6:45 PM Martin Wege wrote:
>
> On Wed, Aug 23, 2023 at 1:06 AM Roland Mainz via Cygwin
> wrote:
> >
> > On Tue, Aug 22, 2023 at 4:52 PM Lavrentiev, Anton (NIH/NLM/NCBI) [C]
> > via Cygwin wrote:
> > > > FIFOs which don't make *any* sense
> > > > ... FWIW, a remote NFS fil
On Fri, Aug 25, 2023 at 2:19 PM Corinna Vinschen via Cygwin
wrote:
>
> On Aug 23 01:05, Roland Mainz via Cygwin wrote:
> > Note that Cygwin does not interpret the file |myfifo.fifo| as FIFO,
> > instead it comes back as a symlink "myfifo.fifo -> ':\0:c4:1000'".
> >
> > AFAIK there are (at least) t
On Sat, Aug 26, 2023 at 4:16 PM Corinna Vinschen via Cygwin
wrote:
>
> On Aug 26 13:26, Cedric Blancher via Cygwin wrote:
> > On Fri, 25 Aug 2023 at 14:26, Corinna Vinschen via Cygwin
> > wrote:
> > >
> > > On Aug 25 14:18, Corinna Vinschen via Cygwin wrote:
> > > > On Aug 23 01:05, Roland Mainz
> You don't seem to understand the problem.
I think I do, and that aligns with your explanation how Cygwin machinery works
to fake the FIFOs.
> If I can recognize a file as FIFO, I can use it as FIFO, regardless if it's a
> native FIFO or a Cygwin FIFO.
That's exactly what I meant!
> Show m
On Aug 26 14:15, Lavrentiev, Anton (NIH/NLM/NCBI) [C] via Cygwin wrote:
> > This thread is not about send() blocking or returning EAGAIN. This
> > is about the behaviour of select(2) and poll(2).
>
> I was merely commenting on your note that if select() returned a socket as
> writable, and send()
On Aug 25 23:21, Lavrentiev, Anton (NIH/NLM/NCBI) [C] via Cygwin wrote:
> > it is not possible to diffentiate between Cygwin
> > FIFOs and real FIFOs created from the remote side in `ls -l'
> > output.
>
> Why would that be necessary? If it's a FIFO, it can be used as a
> FIFO, regardless where a
> This thread is not about send() blocking or returning EAGAIN. This
> is about the behaviour of select(2) and poll(2).
I was merely commenting on your note that if select() returned a socket as
writable, and send() writes more than internally allowed, then send() would
block.
It wouldn't! It'd
On Aug 26 13:26, Cedric Blancher via Cygwin wrote:
> On Fri, 25 Aug 2023 at 14:26, Corinna Vinschen via Cygwin
> wrote:
> >
> > On Aug 25 14:18, Corinna Vinschen via Cygwin wrote:
> > > On Aug 23 01:05, Roland Mainz via Cygwin wrote:
> > > > 2. Check whether the filesystem for the fifos path is NF
> > Can we use send(sock, "", 0) to reenable FD_WRITE, perhaps?
>
> Your idea seems to work. The following patch looks to solve the issue.
> Is it supposed to be any side effect()?
IMO you're triggering an undefined (or not well-defined) behavior, because of
the murky status
of the byte count of
On Aug 25 22:50, Mark Geisert via Cygwin wrote:
> Hi Corinna,
>
> Corinna Vinschen via Cygwin wrote:
> > On Aug 24 14:39, Mark Geisert via Cygwin wrote:
> > > Denis Excoffier via Cygwin wrote:
> > > > Hello,
> > > > When i try to compile coreutils-9.3 under cygwin-3.4.8 i get the
> > > > followin
On Aug 25 23:27, Lavrentiev, Anton (NIH/NLM/NCBI) [C] via Cygwin wrote:
> > While select indicates that
> > data can be written, it doesn't indicate how much data can be written.
> > I. e., if select returns, and there's only buffer space for 10 bytes,
> > and the send call tries to send 100 bytes,
On Fri, 25 Aug 2023 at 17:15, Roland Mainz via Cygwin wrote:
>
> On Fri, Aug 25, 2023 at 2:18 PM Corinna Vinschen via Cygwin
> wrote:
> >
> > On Aug 23 01:05, Roland Mainz via Cygwin wrote:
> > > Note that Cygwin does not interpret the file |myfifo.fifo| as FIFO,
> > > instead it comes back as a
On Fri, 25 Aug 2023 at 14:26, Corinna Vinschen via Cygwin
wrote:
>
> On Aug 25 14:18, Corinna Vinschen via Cygwin wrote:
> > On Aug 23 01:05, Roland Mainz via Cygwin wrote:
> > > 2. Check whether the filesystem for the fifos path is NFS
> > > (cgywin.dll's |fs.fs_is_nfs()|), and then just refuse |
The following Perl distributions have been updated to their latest
release version available on CPAN:
noarch
--
perl-Business-ISBN-Data-20230822.001-1
perl-Mozilla-CA-20230821-1
perl-URI-5.21-1
--
*** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO ***
If you want to unsubscribe from th
This is an update to the latest upstream release of xfig (including
fig2dev/transfig).
--
*** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO ***
If you want to unsubscribe from the cygwin-announce mailing list, look
at the "List-Unsubscribe: " tag in the email header of this message.
Send emai
18 matches
Mail list logo
