public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: NFS mkfifo support in cygwin 3.5.0
Date: Sat, 9 Sep 2023 23:33:26 +0200	[thread overview]
Message-ID: <ZPzkphZ6U931ypcs@calimero.vinschen.de> (raw)
In-Reply-To: <ZPuEmZlxpI9twFNa@calimero.vinschen.de>

On Sep  8 22:31, Corinna Vinschen via Cygwin wrote:
> On Sep  8 12:59, Corinna Vinschen via Cygwin wrote:
> > On Sep  8 06:48, Cedric Blancher via Cygwin wrote:
> > > So chmod() for a FIFO inode on NFS fails. Tested with MSFT NFSv3 and
> > > new builds of the NFSv4.1 ms-nfs41-client filesystems.
> > 
> > Did you actually test this with 3.4.8?  It never worked on NFS.
> > 
> > Just to be clear, the above creates a Cygwin FIFO.  The situation
> > is different with native FIFOs, created on the host.  With those,
> > chmod worked before because native FIFOs were handled like normal files,
> > except in stat(2).  Now that they are handled as FIFOs, the mechanism
> > to change the file mode doesn't work anymore, because it depends on
> > FIFOs being WIndows shortcuts.
> > 
> > I will look into that at one point, but it's not a regression.
> 
> For the records:
> 
> Fixing this for native FIFOs is relatively easy. Fixing this for Cygwin
> emulated FIFOs is rightout impossible ATM:
> [...]

I found a solution by switching Cygwin FIFOs on NFS from symlinks to
shortcut files.  I disabled symlink FIFOs entirely, so you have to
remove the Cygwin FIFOs you created on NFS in the last days and create
them anew.

The patches are in the test release cygwin 3.5.0-0.432.g5bbe0e56c617
and later.

> I'll be offline for some time now for personal reasons, 

That's definitely true starting right now.


Corinna

      reply	other threads:[~2023-09-09 21:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-06 15:25 [ANNOUNCEMENT] cygwin 3.4.9-1 Corinna Vinschen via Cygwin-announce
2023-09-07 21:20 ` NFS mkfifo support in cygwin 3.5.0 " Martin Wege
2023-09-08  4:48   ` Cedric Blancher
2023-09-08 10:59     ` Corinna Vinschen
2023-09-08 20:31       ` Corinna Vinschen
2023-09-09 21:33         ` Corinna Vinschen [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ZPzkphZ6U931ypcs@calimero.vinschen.de \
    --to=corinna-cygwin@cygwin.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).