named-pipes

问题 I wrote a code in C#, which works great at my computer, with Windows 7 (MS SQL Server 2008) but not at the other with Windows Vista (MS SQL Server 2005). I can not change system on the second computer ;) I'm using Visual Studio 2010. So this is the part of code, from my class "obSQL": private SqlConnection connection; public obSQL(string user, string pass, string instance, string dbdir) //sql server authentication { connection = new SqlConnection(); connection.ConnectionString = "user id=" +

问题 I have NamedPipeClientStream which connects to NamedPipeServerStream. They exchange a couple of messages, and then NamedPipeClientStream closing, while NamedPipeServerStream recreated and continue listening for the client pipes. (I couldn't make a working async Server Pipe, so this is some kind of dog-nail) The client-server interaction works fine during my client's streams launched from normal user sessions. But there are a situation when Client pipe is launched from session 0 on Win7 and

问题 On our Linux system we use named pipes for interprocess communication (a producer and a consumer). In order to test the consumer (Java) code, I would like to implement (in Java) a dummy producer which writes to a named pipe which is connected to the consumer. Now the test should also work in the Windows development environment. Thus I would like to know how to create a named pipe in Windows from Java. In Linux I can use mkfifo (called using Runtime.exec() ), but how should I do this on

问题 I'm using Python2.7, the SPARC ASP solver, and am running my code from the Ubuntu14.04 command line. I'm trying to set up two-way communication between my Python code and my ASP (answer-set-programming) code. To do this I am sending queries from python to ASP, putting the ASP response into a fifo pipe, and in the python code the contents of the fifo is read into a string and that string is then written to a text file (this is so that I can check the text file to see if I'm getting the output

问题 I'm trying to narrow down the cause of this issue and have run into some behaviour I didn't expect. I'm running Node v11.8.0 on Ubuntu 18.04.1 LTS. If I run this script: const fs = require('fs'); const { promisify } = require('util'); const { spawn, spawnSync, execSync } = require('child_process'); const { O_RDWR } = fs.constants; const pipePath = "/tmp/myPipe"; let pipeHandle; let stream; function pipeListener(data) { console.log("Pipe data received", data.length); } async function setupPipe

问题 I have a script which have their input/output plugged to named pipes. I try to write something to the first named pipe and to read the result from the second named pipe but nothing happen. I used open then open2 then sysopen whithout success : sysopen(FH, "/home/Moses/enfr_kiid5/pipe_CGI_Uniform", O_RDWR); sysopen(FH2, "/home/Moses/enfr_kiid5/pipe_Detoken_CGI", O_RDWR); print FH "test 4242 test 4242" or die "error print"; doesn't made error but didn't work : i can't see trace of the print,

问题 I have a very simple basic program that has two process first one is parent and second one is child . Child process should write some stuff to the FIFO . After all writing jobs finished(after the child is terminated). Then parent process should read all the FIFO file and print to the stdout . So I think, I need a wait(NULL); for parent . So the parent will wait until the child is terminated. But child is also blocked because of the writing and blocked for reading this writes. So both process

问题 Hi, We have a winform application that is only to be executed as a singelton, If a second instance try to start this new instance will connect to the current and transmit parameters over namedpipes. The problem is that when starting the first instance there will be a try to connect to existing host. If the host is not existing(like in this case) an exception will be thrown. There is no problem to handle this exception but our developers is often using "Break on Exception" and that means that

问题 Hi, We have a winform application that is only to be executed as a singelton, If a second instance try to start this new instance will connect to the current and transmit parameters over namedpipes. The problem is that when starting the first instance there will be a try to connect to existing host. If the host is not existing(like in this case) an exception will be thrown. There is no problem to handle this exception but our developers is often using "Break on Exception" and that means that

问题 I am trying to make a Windows Service that simply sits and listens for messages on a named pipe. But it's not working. Trying to connect to the named pipe simply times out, and when I view the process handles of the service's process in Process Explorer, I do not see the named pipe. Here is what I have so far: namespace Service { class Service : ServiceBase { Thread workerThread; static bool serviceStarted = false; static PipeSecurity pipeSecurity = new PipeSecurity(); public Service() { this