From: Brian Inglis <Brian.Inglis@Shaw.ca>
To: cygwin@cygwin.com
Cc: Martin Wege <martin.l.wege@gmail.com>
Subject: Re: 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
Date: Sat, 26 Aug 2023 13:16:29 -0600 [thread overview]
Message-ID: <376806b2-4228-085b-b45e-a48fd443ae0d@Shaw.ca> (raw)
In-Reply-To: <CANH4o6Mo3yTteiQejaEaVnUQrJEAXh5N4fxKoPQHjtgr-dnC8Q@mail.gmail.com>
On 2023-08-26 11:44, Martin Wege via Cygwin wrote:
> On Fri, Aug 25, 2023 at 2:19 PM Corinna Vinschen via Cygwin
> <cygwin@cygwin.com> 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!
Feel free to submit doc patches if you feel there is a lack.
We are all volunteers here - and that includes you!
--
Take care. Thanks, Brian Inglis Calgary, Alberta, Canada
La perfection est atteinte Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter not when there is no more to add
mais lorsqu'il n'y a plus rien à retirer but when there is no more to cut
-- Antoine de Saint-Exupéry
next prev parent reply other threads:[~2023-08-26 19:16 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-07 14:42 Martin Wege
2023-08-07 18:26 ` Brian Inglis
2023-08-07 19:14 ` Corinna Vinschen
2023-08-07 21:14 ` Martin Wege
2023-08-08 8:20 ` Corinna Vinschen
2023-08-08 19:38 ` Martin Wege
2023-08-09 8:01 ` Corinna Vinschen
2023-08-09 9:12 ` Martin Wege
2023-08-09 9:56 ` Corinna Vinschen
2023-08-10 12:49 ` Martin Wege
2023-08-18 4:02 ` Martin Wege
2023-08-18 8:34 ` Corinna Vinschen
2023-08-18 13:14 ` Martin Wege
2023-08-21 4:49 ` Cedric Blancher
2023-08-21 8:37 ` Corinna Vinschen
2023-08-22 14:52 ` [EXTERNAL] " Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2023-08-22 23:05 ` How to fix |mkfifo()| failure if |pathname| is on NFS ? / was: " Roland Mainz
2023-08-24 16:45 ` Martin Wege
2023-08-25 4:25 ` Cedric Blancher
2023-08-26 17:58 ` Martin Wege
2023-08-25 12:18 ` Corinna Vinschen
2023-08-25 12:25 ` Corinna Vinschen
2023-08-26 11:26 ` Cedric Blancher
2023-08-26 14:15 ` Corinna Vinschen
2023-08-26 17:40 ` Martin Wege
2023-08-26 19:16 ` Brian Inglis
2023-08-25 15:14 ` Roland Mainz
2023-08-26 11:27 ` Cedric Blancher
2023-08-25 23:21 ` Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2023-08-26 14:28 ` Corinna Vinschen
2023-08-26 14:39 ` Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2023-08-26 17:44 ` Documenting Cygwin on NFS, no longer only exchange-medium! " Martin Wege
2023-08-26 19:16 ` Brian Inglis [this message]
2023-08-27 12:35 ` Corinna Vinschen
2023-08-28 5:35 ` Cedric Blancher
2023-08-28 10:02 ` Corinna Vinschen
2023-08-28 11:41 ` Joshuah Hurst
[not found] ` <14a692f6-7244-4a7e-a69b-d14521fb01e8@secure-endpoints.com>
2023-08-23 17:39 ` Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2023-08-24 5:28 ` Cedric Blancher
2023-08-24 16:40 ` Martin Wege
2023-08-21 12:12 ` Martin Wege
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=376806b2-4228-085b-b45e-a48fd443ae0d@Shaw.ca \
--to=brian.inglis@shaw.ca \
--cc=cygwin@cygwin.com \
--cc=martin.l.wege@gmail.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).