You could open() your pipe O_RDONLY | O_NONBLOCK, and if you want the C stream, you can get it with fdopen(). However, there might be a problem with the select() – AFAIK, a pipe fd open for reading that has no writer is always prepared for reading, and read() returns 0, so the select() would … Read more
You can write a multi threaded pipe server by repeatedly creating a NamedPipeServerStream and waiting for one connection, then spawning a thread for that instance of NamedPipeServerStream. You can only have 254 concurrent clients though according to the .NET MSDN documentation linked below. For Win32 APIs though you can pass a special value to get … Read more
In typical UNIX fashion, read(2) returns 0 bytes to indicate end-of-file which can mean: There are no more bytes in a file The other end of a socket has shutdown the connection The writer has closed a pipe In your case, fifo.read() is returning an empty string, because the writer has closed its file descriptor. … Read more
This is expected behaviour of pipes. It is supposed to hang untill other process connects to the pipe and reads it.
Your endpoint looks fine, although I’m curious about what’s in localBinding… Sounds like the easiest option is to just change the endpoint configuration on the named pipes client to match your service endpoint. The client shouldn’t care as long as it’s the only endpoint in the clients config file. Otherwise you’ll have to add names … Read more
I think that at least some of progress reports gets silenced when output is not a terminal (tty). I’m not sure if it applies to your case, but try to pass –progress option to ‘git clone’ (i.e. use git clone –progress <repository>). Though I don’t know if it is what you wanted to have.
Try this before ReadFile : BOOL WINAPI PeekNamedPipe( __in HANDLE hNamedPipe, __out_opt LPVOID lpBuffer, __in DWORD nBufferSize, __out_opt LPDWORD lpBytesRead, __out_opt LPDWORD lpTotalBytesAvail, __out_opt LPDWORD lpBytesLeftThisMessage ); if(TotalBytesAvail > 0) ReadFile(….); -AV-
There are two things which can cause the instantiation of a second or subsequent NamedPipeServerStream on the same pipe to fail: the maxNumberOfServerInstances ctor argument must have been set to more than 1 when the first instance of the pipe server was created. If not, the second call will fail unless the first instance has … Read more
i had the same issue. go to Sql Server Configuration management->SQL Server network config->protocols for ‘servername’ and check named pipes is enabled.
That’s just the way it’s defined. From the Open Group page for the open() function O_NONBLOCK When opening a FIFO with O_RDONLY or O_WRONLY set: If O_NONBLOCK is set: An open() for reading only will return without delay. An open() for writing only will return an error if no process currently has the file open … Read more