From: Martin Wege <martin.l.wege@gmail.com>
To: cygwin@cygwin.com, Corinna Vinschen <corinna-cygwin@cygwin.com>
Subject: Re: mkfifo: cannot set permissions of 'x.fifo': Not a directory
Date: Mon, 21 Aug 2023 14:12:00 +0200 [thread overview]
Message-ID: <CANH4o6OQhxG4hAxKBQPoht0S+3PG3WGPar-dcJ1MXQ2LDd71xA@mail.gmail.com> (raw)
In-Reply-To: <ZN8tK/mATx6KbQWk@calimero.vinschen.de>
On Fri, Aug 18, 2023 at 10:34 AM Corinna Vinschen
<corinna-cygwin@cygwin.com> wrote:
>
> On Aug 18 06:02, Martin Wege via Cygwin wrote:
> > On Mon, Aug 7, 2023 at 4:42 PM Martin Wege <martin.l.wege@gmail.com> wrote:
> > >
> > > Hello,
> > >
> > > We get a weird mkfifo failure in Cygwin on NTFS:
> > >
> > > /usr/bin/mkfifo -m 600 x.fifo
> > > mkfifo: cannot set permissions of 'x.fifo': Not a directory
> > >
> > > Is there a known workaround? So far named fifos cannot be created somehow.
> >
> > This is fixed for NTFS, but still broken for Windows builtin NFS v3 client:
>
> It was actually never supposed to work on NFS. Cygwin FIFOs are
> created as symlinks of the type Windows shortcut with the R/O attribute
> set. Those are only generated on NTFS and FAT filesystems. NFS symlinks
> are generated using special magic. NFS doesn't support DOS attributes.
NFS supports symlinks!
Easy solution would be to say that symlinks on NFS pointing to
:\0:c4:$inodenum are pipes on the local Cygwin machine.
/usr/bin/mkfifo on Cygwin creates a symlink :\0:c4:$inodenum. Cygwin
stat() functions turn symlinks with a value of :\0:c4:... to pipes.
Everyone is happy!
It does not have to be portable across different platforms. Just
portable enough that mkfifo in with bash scripts works on NFS.
Thanks,
Martin
>
> Corinna
prev parent reply other threads:[~2023-08-21 12:12 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
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 [this message]
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=CANH4o6OQhxG4hAxKBQPoht0S+3PG3WGPar-dcJ1MXQ2LDd71xA@mail.gmail.com \
--to=martin.l.wege@gmail.com \
--cc=corinna-cygwin@cygwin.com \
--cc=cygwin@cygwin.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).