named-pipes

问题 Here's a general example of what I need to do: For example, I would initiate a back trace by sending the command "bt" to GDB from the program. Then I would search for a word such as "pardrivr" and get the line number associated with it by using regular expressions. Then I would input "f [line_number_of_pardriver]" into GDB. This process would be repeated until the correct information is eventually extracted. I want to use named pipes in bash or python to accomplish this. Could someone please

问题 How can I send a multiline string with blank lines over a NamedPipe? If I send a string string text= @"line 1 line2 line four "; StreamWriter sw = new StreamWriter(client); sw.Write(text); I get on the server side only "line 1" : StreamReader sr = new StreamReader(server); string message = sr.ReadLine(); When I try something like this StringBuilder message = new StringBuilder(); string line; while ((line = sr.ReadLine()) != null) { message.Append(line + Environment.NewLine); } It hangs in the

问题 I have two projects: one runs on c++ and one runs on c-sharp. For some reason, when I try c++ to C++ server and client works fine, same if I tried c=sharp and c-sharp, The problem comes when I try C-sharp with c++. Here is the server code in c-sharp: using System; using System.IO; using System.IO.Pipes; class PipeServer { static void Main() { using (NamedPipeServerStream pipeServer = new NamedPipeServerStream("\\\\.\\pipe\\mypipe", PipeDirection.Out)) { Console.WriteLine(

问题 I have this simple set up: pwd /home/abc/pipetest ls mydir pipetest.sh Now I do: ./pipetest.sh And then I get ls file.tar.bz2 mydir pipe pipetest.sh My question is: Why did the file named pipe get created? It contains some characters that could not be seen using vi. What's going on? pipetest.sh contains: #!/bin/sh directory_name=mydir tar cf pipe $directory_name bzip2 -c < pipe > file.tar.bz2 回答1: tar cf pipe $directory_name writes the tar file to a file named pipe . What you want to do is

问题 When creating named pipes using the NamedPipeClientStream or NamedPipeServerStream classes of dotnet core, the associated "pipe" (which appears to actually be a socket) has "CoreFxPipe_" added to the front of the file name automatically. Is there a non-hacky way to prevent this behavior? I would simply like the file name to be exactly the name I provide to the constructor. In the dotnet core documentation, it describes the following constructor: NamedPipeServerStream(String) Initializes a new

问题 My application uses a Named Pipe to do IPC. What access control should I place on it, to provide broad local only access? The pipe is created by the .net 2.0 remoting protocol, and it already has an ACL for the 'NETWORK' group to deny all access, so I think only local users can access it. In my remoting configuration file I need to pick an 'authorizedGroup' who can access this pipe. I would like any process running on the local machine to access my named pipe. I would appear to need to select

问题 I use some Delegate and Events to Implement NamedPipes like this: public delegate void MessageReceivedHandler(byte[] message, Client client); public event MessageReceivedHandler MessageReceived; void ListenForClients() { //Do some Thread readThread = new Thread(Read) { IsBackground = true }; } void Read(object clientObj) { //Do Some if(MessageReceived != null) MessageReceived(ms.ToArray(),client); } When I Use this event in Form Class(Inherited from Control object) the Implementation is:

问题 I am trying to request a GET through an existing named pipe. This is to work around the fact that Node processes on Azure are wrapped by IISNode, thus not having a port of their own, but rather being given a named pipe (as the PORT environment variable). Node's net.Server class knows how to handle named pipes, which explains why HTTP routing works fine (as http .Server` seems to use the same interface). From the docs: Class: net.Server on server.listen(path[, callback]) On Windows, the local

问题 As part of our Integration build we are installing sql server 2008 on a machine then deploying various software on it. One piece of software requires that Net Named pipes is enabled for it to install. As the server is built automatically as part of our continuous build process, we have to be able to do this via a non-interactive command line. Does anyone know of a way to enable the named pipes within the "Sql Server Network Configuration" section without a gui? (I.e. Command line only) 回答1: I

问题 I am currently evaluating named pipes for IPC on Windows with .NET/C#. I am currently looking at a single producer, single consumer scenario. Are there any good performance consideration guidelines? In my first test case I was comparing the speed of large messages vs small messages and seems to be that large (64k) messages are sent as quick as small (48 Bytes) packages. This was with the default parameters. I might add more test scenarios, but this is quite time-consuming and thus I am