Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!snorkelwacker.mit.edu!bloom-beacon!dont-send-mail-to-path-lines
From: tomt@maui.coral.COM (Tom Tulinsky)
Newsgroups: comp.windows.x
Subject: A tool to monitor X traffic between client and server
Message-ID: <9104021501.AA24897@maui.coral.com>
Date: 2 Apr 91 15:01:44 GMT
References: <9103282101.AA01885@dink.ease.arco.com>
Sender: daemon@athena.mit.edu (Mr Background)
Organization: The Internet
Lines: 35


) Return-Path: <uunet!expo.lcs.mit.edu!xpert-mailer>
) Date: Thu, 28 Mar 91 15:01:39 -0600
) From: uunet!arco.com!rseaney (Rick Seaney)
) To: xpert%expo.lcs.mit.edu@arco.com
) Subject: A tool to monitor X traffic between client and server
) 
) 
)   I'm looking for a tool to monitor traffic between an X client and server.
)   I heard that there was a utility called xscope, when I brought it over
)   it had something to do with signal processing.  Please mail responses to
) 
) 	rseaney@ease.arco.com
) 			Thanks	
) 
The xscope that monitors client-server traffic is part of the MIT
contrib/clients distribution.  I built and it works (on a Sun SS1
running MIT X11r4).  To make it build I had to say 
   make TOP=/usr/x11r4/src/mit
which is where we place our MIT X tree.

To monitor "anyxclient" from the same machine as the client, do 
    xscope -i1 -v2
    anyxclient -display unix:1.0 



 Coral
     * **	Tom Tulinsky                508 460-6010
  *  **		Coral Network Corporation   fax 508 481-6258
*  ** 		734 Forest St               net: tomt@coral.com
 ***		   Marlboro, MA 01752		
  **		   U S A
*********	   Overheard in a BART station:
NETWORKS	      "I was the only NORM there!"