NamedPipeServerStream creates a socket not a fifo on ubuntu

[huiguochen]

I expected to use NamedPipeServerStream to create a fifo file on linux, but it created a socket Named "CoreFxPipe_1.fifo" in /tmp directory.
here is test code:

            NamedPipeServerStream fifo = new NamedPipeServerStream("1.fifo",PipeDirection.InOut);
            fifo.WaitForConnection();

what is the reason? how to create a fifo on linux?

[EDIT] Add C# syntax highlighint by @karelz

[mikedn]

See https://github.com/dotnet/corefx/issues/1849

[eerhardt]

Thanks @mikedn. #14633 answers this question, and along with the description of the PR that changed from fifo to sockets - dotnet/corefx#6833.

Closing as this is answered.

[DrSensor]

Any workaround or specific param like NamedPipeServerStream("1.fifo", PipeDirection.Out, fifo: true) to use linux named pipe instead of unix socket? It break the compatibility when in use for communicating between 2 different programming language.

FYI: Windows 10 now support unix socket

[eerhardt]

You can use the Mono.Posix.NetStandard library on .NET Core to get access to the mkfifo POSIX command. This will allow your program to read/write to a FIFO/Unix named pipe.

Regarding Windows 10 now supporting unix domain sockets, .NET Core allows that as well if you are running on a Windows 10 machine that has support for UDS. See dotnet/corefx#27631 for the PR that added support for it.