Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!elroy.jpl.nasa.gov!suned1!jht
From: jht@suned1.Nswses.Navy.MIL (James H Tibbs)
Newsgroups: comp.windows.x
Subject: net monitoring via X
Keywords: Using X-term for OW and DECWindows clients.
Message-ID: <8642@suned1.Nswses.Navy.MIL>
Date: 18 Mar 91 22:53:18 GMT
Reply-To: jht@suned1.nswses.navy.mil (James H Tibbs)
Distribution: usa
Organization: US Navy (NSWSES), Port Hueneme, CA.
Lines: 21

HI,

   My question(s) revolves around using an X-term to 
monitor our local network consisting of both Suns
and VMS machines. The networking group (I am a part 
of the "systems" group) would like to be able to to 
launch X-clients from both the VMS environment (DecWindows, 
DECnet and Wollongong) as well as the Sun environment (OpenWindows 
X and 'vanilla' MIT stuff) and run them concurrently on a single 
X-term. The clients, I assume, would be of the network monitor/tool 
variety.  Now, with X, this should not be a problem...right? 
Well, I have come to understand that there are just enough 
violations of the X spec, especially in VMS land, to make this 
a bit tricky.  Can anyone tell me about their experiences doing 
similar things with X....any gotchas...? If you are running 
such tools on an X-term what are you using (commercial or PD?). 
  As the sole X-user (NCD16....for admin of Suns) here on 'campus' 
I am working with our networking people to help upgun thier network 
monitoring tools with an X based solution.

Any info appreciated!