Message-Id: <200508111052.j7BAqWr7017597@delorie.com> Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com From: "Herb Martin" To: Subject: RE: Is there a UNIX socket test client program (a la NetCat)? Date: Thu, 11 Aug 2005 05:52:31 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit In-Reply-To: <42FB2939.42E141D2@dessent.net> > It probably depends on what you want to do, and the examples > section of the man page is a good place to look. It could be > as simple as: > > socat - UNIX-CONNECT:/var/run/foo.sock > > That should connect stdin/stdout to the socket, in the same > way as netcat. socat really just boils down to specifying > two things to connect together, and each of those can be any > of the various types and take a myriad of options. That is precisely what I wanted to do -- and even though I believe that I had tried this there was a syntax error in both my cygrunsrv defintion for spfd AND in my socat - commands. Once I knew this was the syntax for socat then I concentrated better on looking for errors (missing ":" colon between the connect and the file socket name.) Thanks once again. Now, I have a way to test for such silly errors on my part and for general functioning of UNIX-type sockets (and a bunch of other stuff as well.) This really is a big help. Being rather new to Posix style systems, the unix-socket stuff was too much of a black box without some type of test tool. -- Herb Martin -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/