X-Recipient: archive-cygwin AT delorie DOT com DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 1F89B385734F DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com; s=default; t=1693071914; bh=EW6Jr3zCb8PVDZIVVH1xF02tGSDkooi0ykEFK+7GzrQ=; h=References:In-Reply-To:Date:Subject:To:Cc:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: From:Reply-To:From; b=P+pwaNk25Tkm5GbTd4b1WnshObeTsvTLBsdeLtCQKrbWw/DccUeoQAdNzcaCnfawC Pugvb4WGR0cMfpSXJtYNrGlL0Dqxl9nrcAXmzwGKAUcl+iSSdnOVcZXAHD1fMirXAA IDkR5NqlkPBTpx354EJDsKFSLkmlitM3GD75Aljc= X-Original-To: cygwin AT cygwin DOT com Delivered-To: cygwin AT cygwin DOT com DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 405A53858416 X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1693071872; x=1693676672; h=content-transfer-encoding:cc: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=zD9wkYtahAvCHcuvzD1tDMI3coB6LX2E9S19Rk9qtaU=; b=BmqzzAo8sIlnK1QbUBrppJ/aeaq4RdCw3edOdFX1cakKwhGcyCoQ6u0TMkO0SA1npj 5jc0GuQ+EBtGXT/HJN/bG+0BwWSpnOC9GlQUuVeEeTJ5NKf/BPM8sNc7LLOOiCX/Q0dE ASqc35Ts9h+inCozseCAmltdQ44vVJ5TUYum1ECn0fNgQ20YY1EjMbiFH5H9MEUNnwrM yiOuv0CgpPxg/8Hs/QWDe9JS5LnQAAKOVurCaKvfZL/Z1p7FQZilTpR6bAEBY2/NjQKK 2XzQYwPKuQqu6ewtiEEBzV/cXG8L9N+MP6vRVxU03eOWtIqS+2b1V+WbhzPS2jV/JXg8 indA== X-Gm-Message-State: AOJu0Yw1Ftx6ljNLLWP43r05efQ5ODDPWEwKZEMYMwmJ3C2HfIUKfvF3 b1ZGUn5Mw+uD3zc5XXL2sM4e8Veb567jbeWrLw0o3kpXdEtGsw== X-Google-Smtp-Source: AGHT+IE2YffMrJECgoaPyk+BFIvAO2XcFVVbo7+m+U25Pl7jaFm/DiED4iUGJLkSyR3MtCkhw37w2VMq+evKhpPBP2I= X-Received: by 2002:a05:6870:828e:b0:1bf:d05f:f77 with SMTP id q14-20020a056870828e00b001bfd05f0f77mr6549859oae.48.1693071872348; Sat, 26 Aug 2023 10:44:32 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: Date: Sat, 26 Aug 2023 19:44:21 +0200 Message-ID: Subject: Documenting Cygwin on NFS, no longer only exchange-medium! 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 To: cygwin AT cygwin DOT com Cc: Corinna Vinschen 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, PLING_QUERY, 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 List-Archive: List-Post: List-Help: List-Subscribe: , From: Martin Wege via Cygwin Reply-To: Martin Wege Content-Type: text/plain; charset="utf-8" Sender: "Cygwin" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by delorie.com id 37QHjEWn015990 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) these two options to fix the problems: > > 1. Check whether the filesystem for the fifos path is NFS > > (cgywin.dll's |fs.fs_is_nfs()|), and if it is a symlink check if it > > starts with ':\0:c4:' (assuming "c4" is the prefix for inodes created > > with |mkfifo()|). If this condition is |true|, then cygwin |stat()|, > > |open()| etc. should treat this inode as FIFO. > > The downside is that it is not possible to diffentiate between Cygwin > FIFOs and real FIFOs created from the remote side in `ls -l' > output. Note that Cygwin returns the NFS stat info verbatim, so > a real FIFO is returned as a real FIFO: > > linux$ mkfifo bar > cygwin$ ls -l bar > prw-r--r-- 1 corinna vinschen 0 Aug 25 13:58 bar > > The idea was always to use NFS as exchange medium, but not as > installation medium for the entire distro or to keep Cygwin home > dirs on NFS. There were times where NFS was pretty unstable. > I used NFS for quite some time to build Cygwin packages, but at one > point I got trouble (performance problems with multiple concurrent > processes accessing an NFS share, build errors out of the blue), > so I switched to Samba shares, albeit grudgingly. I'm not yet > sure if the problems are fixed. At least a recent OpenSSH build > ran through without problems... Corinna, could you please update the Cygwin documentation then? We use NFS, both Windows builtin and CITI NFSv4.1, with Cygwin for years without major problems, so that comment about exchange-medium-only is clearly wrong! 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