X-Recipient: archive-cygwin AT delorie DOT com DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org EB332385842C DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com; s=default; t=1693060169; bh=SJgGqfRiJWto2qo/uh7uCWZm07H3+7/Qbq/dGdT+PYY=; h=Date:To:Subject:References:In-Reply-To:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:Cc: From; b=ZL+kQZqwsY4PJUNstYmPGVAPS9mwaFC3vm+/FGUhrrN0Q/seul1QS1sq45w++4RJH 2rGJa6WRnoj8ax6kiCfWZuJwMh7UvwnUclE6JgwVkv1KkuGyDDLTLIrC4ORquonngv +EwejlA7ucSsLXhJ1icfmDCqGighezqMy7Hftzyg= X-Original-To: cygwin AT cygwin DOT com Delivered-To: cygwin AT cygwin DOT com DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 0085B3858C53 Date: Sat, 26 Aug 2023 16:28:53 +0200 To: cygwin AT cygwin DOT com Subject: Re: How to fix |mkfifo()| failure if |pathname| is on NFS ? / was: Re: [EXTERNAL] Re: mkfifo: cannot set permissions of 'x.fifo': Not a directory Message-ID: Mail-Followup-To: cygwin AT cygwin DOT com References: MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: X-BeenThere: cygwin AT cygwin DOT com X-Mailman-Version: 2.1.29 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Corinna Vinschen via Cygwin Reply-To: cygwin AT cygwin DOT com Cc: Corinna Vinschen Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com Sender: "Cygwin" 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 and how it was created.. You don't seem to understand the problem. A Cygwin FIFO is not a real FIFO. We're running on Windows, right? Show me how to create a FIFO on NTFS or FAT by OS calls only, please. Cygwin's way of creating FIFOs is to create a Cygwin syumlink with special content which in turn is faked to be a FIFO when running Cygwin's stat(2) call. Usually that's a Windows shortcut (one of the .lnk thingies), but on NFS we create a real symlink with weird content *accidentally*, because that's how we create symlinks on NFS, and nobody ever cared to that anyway. Again, there is no API to create native FIFOs on a remote NFS filesystem. But, ultimately, you're still right. 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. This just isn't done yet. Corinna -- 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