From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <corinna@sourceware.org>
Received: by sourceware.org (Postfix, from userid 2155)
	id DED553858D1E; Sat,  9 Sep 2023 21:33:27 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org DED553858D1E
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
	s=default; t=1694295207;
	bh=CEr4HDVC1mK/g7VvDKPHUPZU98WKy+kd17NRtmZ9aXQ=;
	h=Date:From:To:Subject:Reply-To:References:In-Reply-To:From;
	b=crsk0qG0ytEgxDEOIQYZeUAKh86yfuWTyQiHOjKPujqsvqzmcgZcJP13B+/9wC+9e
	 JJGrVTK9f6VdvghBkAtvL6o1OtfoeLc/GUilnxVXDVrTSioT09+148GEzkgZ5YkHyf
	 otlD+BTJnj2CU+mwc0l0yuU2kXKUFyVo9D0iTS28=
Received: by calimero.vinschen.de (Postfix, from userid 500)
	id 34150A80851; Sat,  9 Sep 2023 23:33:26 +0200 (CEST)
Date: Sat, 9 Sep 2023 23:33:26 +0200
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: NFS mkfifo support in cygwin 3.5.0
Message-ID: <ZPzkphZ6U931ypcs@calimero.vinschen.de>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <announce.20230906172530.526501-1-corinna-cygwin@cygwin.com>
 <CANH4o6MSXBxMBsqgtWbNe9rPETNgY-D5QxJO9AsLwe+tm0WkDw@mail.gmail.com>
 <CALXu0UcRuepZC_jH1+rzqLxDuhCtC4h94wgfVxkBxH9fSDEH7A@mail.gmail.com>
 <ZPr+mFTvEfYfD+8T@calimero.vinschen.de>
 <ZPuEmZlxpI9twFNa@calimero.vinschen.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <ZPuEmZlxpI9twFNa@calimero.vinschen.de>
List-Id: <cygwin.cygwin.com>

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