X-Recipient:	archive-cygwin AT delorie DOT com
DKIM-Filter:	OpenDKIM Filter v2.11.0 sourceware.org EDC813857C5A
DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
	s=default; t=1692895279;
	bh=mNqzDu1WlRVWsF3hG8SQ5xufhfSIhIoLackXlK/3k6U=;
	h=References:In-Reply-To:Date:Subject:To:List-Id:List-Unsubscribe:
	List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:
	From;
	b=LEDnH2DfMflJeF1DHd3AmkQWMDefeMx0X7Bmrk3QkOdd5JYCuE3SxL+N/Kg2txIC2
	jVAhjhbnZiZJW5bXKd1mXj1FimS5WzHkUCQw1jKrfesztjkE40xcKWisyaC1NEHSOP
	gJSRcjRH2L+zPe0ujwpENoCCu1u1iI0S2/r2bHh4=
X-Original-To:	cygwin AT cygwin DOT com
Delivered-To:	cygwin AT cygwin DOT com
DMARC-Filter:	OpenDMARC Filter v1.4.2 sourceware.org 141FC3857704
X-Google-DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20221208; t=1692895240; x=1693500040;
	h=content-transfer-encoding:to:subject:message-id:date:from
	:in-reply-to:references:mime-version:x-gm-message-state:from:to:cc
	:subject:date:message-id:reply-to;
	bh=0sJgU04zsZmAxUdzbhmL3CiaZZtuwVv3fT5YmhJrhus=;
	b=SJj7mEjkFSLrc4UFs56U3qAXL30fDNrCU8ROlsd6cmE3tNZCbd8EenE/MTV1XIxJLu
	dGo1kNIm0l69R+L5nbfLKKmtYn9FKvAnzOTHEvI98v1E4j3KJC7Q8yw+eSnUnbl/GVrg
	MOeChCX+7ZhS81MfSFyE0KUiPndHfsnS06FQuylSlUUEfTsSONLvA0qf/3f2K7NxoKLD
	u1+qjKZJZRo/aM39IdbJfl/jHJUONBgKsPOWVRYxQDC5Nm5HRNnQKyXsWBxuCjWvjl/5
	lgPacAxZAIHUI6lf1K27tsUn6Xo+YUt6aVi7+nHT8ao+EltCoDv97+5tIDSmx3RQ2JCC
	mHfA==
X-Gm-Message-State:	AOJu0Yxl/yGWZr3AZAihlW9WGEYTDNwXsZGXofKGTLEgK02CEI2Ry5yP
	QhxygRyz3gQDMTFhjcFuN6p7uZA4dpJE9FmaWqmUp0B0/fBHqSV9
X-Google-Smtp-Source:	AGHT+IGHTKoLWLDms+dt2pfzavV9QuFUvfGwzUAnz2fEwZY+5tW1nG0bI5QJqqUZ4mI68Qx1DeuEvaA1saAv2pFrfdE=
X-Received:	by 2002:a05:6870:63a8:b0:1be:e066:acc with SMTP id
	t40-20020a05687063a800b001bee0660accmr348928oap.50.1692895240220; Thu, 24 Aug
	2023 09:40:40 -0700 (PDT)
MIME-Version:	1.0
References:	<CANH4o6O-8O-iMaHowDuy0y7H=pVfZ-3EvubDmTdjGVSST8FkAQ AT mail DOT gmail DOT com>
	<CANH4o6MnH7gWj7d0vmkhCL5N0BTbkrbtGZGtso43MVZBJLBGtw AT mail DOT gmail DOT com>
	<ZN8tK/mATx6KbQWk AT calimero DOT vinschen DOT de>
	<CALXu0UcByeJHfBWSPEZkmfMqSKkmRT_5ZkxLc25EyhJzN9FUtA AT mail DOT gmail DOT com>
	<ZOMiYcQfb7i8Kc8i AT calimero DOT vinschen DOT de>
	<DM8PR09MB70950FABA8C4DAD80B0EA189A51FA AT DM8PR09MB7095 DOT namprd09 DOT prod DOT outlook DOT com>
	<14a692f6-7244-4a7e-a69b-d14521fb01e8 AT secure-endpoints DOT com>
In-Reply-To:	<14a692f6-7244-4a7e-a69b-d14521fb01e8@secure-endpoints.com>
Date:	Thu, 24 Aug 2023 18:40:29 +0200
Message-ID:	<CANH4o6Ozqq7vSqRv+-PLVWcSDToh3WbJ9_E9obm-7R_6WNz5mw@mail.gmail.com>
Subject:	Re: [EXTERNAL] Re: mkfifo: cannot set permissions of 'x.fifo': Not a
	directory
To:	cygwin AT cygwin DOT com
X-Spam-Status:	No, score=0.4 required=5.0 tests=BAYES_00, DKIM_SIGNED,
	DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, RCVD_IN_DNSWL_NONE,
	SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.6
X-Spam-Checker-Version:	SpamAssassin 3.4.6 (2021-04-09) on
	server2.sourceware.org
X-BeenThere:	cygwin AT cygwin DOT com
X-Mailman-Version:	2.1.29
List-Id:	General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Archive:	<https://cygwin.com/pipermail/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-request AT cygwin DOT com?subject=help>
List-Subscribe:	<https://cygwin.com/mailman/listinfo/cygwin>,
	<mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
From:	Martin Wege via Cygwin <cygwin AT cygwin DOT com>
Reply-To:	Martin Wege <martin DOT l DOT wege AT gmail DOT com>
Sender:	"Cygwin" <cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com>
X-MIME-Autoconverted:	from base64 to 8bit by delorie.com id 37OGfJTI010472

On Wed, Aug 23, 2023 at 5:44 PM Jeffrey Altman via Cygwin
<cygwin AT cygwin DOT com> wrote:
>
> On 8/22/2023 10:52 AM, Lavrentiev, Anton (NIH/NLM/NCBI) [C] via Cygwin
> wrote:
> >> FIFOs which don't make *any* sense
> >> ... FWIW, a remote NFS fileystem.
> > I got an impression that the OP is trying to deploy something (maybe the entire Cygwin) onto an NFS share.  So the named FIFO "file" is also created in there.
> >
> > It's pointless to assume that the FIFO can be used as a communication device between the hosts that can mount the share, but it can be quite feasible to envision a scenario, in which the same host opens the FIFO located on the share from two processes and establish the communication using that special "file" (which is basically a special data-less i-node).
>
> I've been following this thread with quite a bit of curiosity. For those
> who do not know me, I'm the lead developer of the AFS filesystem on
> Windows. There have been requests for more than two decades for AFS
> clients to add support for locally created pipe files because AFS
> volumes are often used as home directories (even on Windows) and so many
> applications allocate a pipe in the home directory as a method of
> inter-process communication or a lock. The problem is that even if the
> intended usage of the file is entirely local, the directory object, the
> directory entry and the allocated inode (or equivalent) is network
> visible.

Who cares? It is up to the user, script or application author to do
'the right thing(tm)'.

>
> What happens when the user executes two copies of an
> application such as PyCharm on two separate machines sharing the same
> home directory? Does the directory entry and inode get reused on startup
> and/or deleted on exit? How does that impact the process instance on the
> other machine? The conclusion I came to long ago is that if pipes are to
> be implemented in a network file system namespace then the pipes must be
> fully functional network pipes. In just about all cases applications can
> be configured to use a non-default paths. In my opinion they should not
> be placed in a shared file system.

Oh my god. Please have this debate at the Austin Group. They do the
POSIX standard. We're here about implementing&using the POSIX
standard.

We only want that mkfifo() works with Cygwin on a NFS filesystem, as
specified in https://pubs.opengroup.org/onlinepubs/009696799/functions/mkfifo.html

My intention was not to invent something new. Just code using mkfifo,
and scripts using /usr/bin/mkfifo, should work on NFS. On UNIX&Linux
this works.

Have a look at https://cygwin.com/pipermail/cygwin/2023-August/254266.html,
sounds like there is a feasible way to implement this.

Thanks,
Martin

-- 
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple

- Raw text -