Re: how to know the session
A poster asked how to see sessions; Dave Thacker requested OS and connection details. Hugo Padilla suggested the Cockpit monitoring tool (onprobe, oncockpit, DISPLAY and xhost setup), noting it was not available for 9.3. Gerd Kaluzinski said it was unsupported and limited to Solaris, HP-UX and AIX, and missed its alarms. Jack Parker corrected the DISPLAY and xhost details. No other method was given.
Auto-generated by Claude from the posts below — may be imperfect; read the full thread.
On Tuesday 01 March 2005 07:48, Susana Barea wrote: > Hello list > > i want to know what session is consuming more cpu. > I've IDS 7.31 > Could we have a few more details about your environment and the sessions you want to monitor? At least the OS and connection methods (tcp or shared memory) that you are using are needed. DT -- Dave Thacker Senior Systems Administrator Omni Hotels Reservation Center V:402-952-6535 F:402-334-8013 M: 402-981-4613 (24/7)
Hi there You can use cockpit, it is an excellent tool for monitoring the database, I used to work with it, lamentably no longer it exists for version 9.3 To use it, first you have to set the environment variable DISPLAY=:0.0 (if you use solaris) where :0.0 is the name of the X server in informix Also you have to give permissions with xhosts + (as root) Then you have to run the daemon (as informix) onprobe service servicename Finally you can run the cockpit client (as informix) oncocpit service servicename
ONCOCKPIT was a very good tool. The best thing was to define own alarms with rules in form of a select on sysmaster database. ONCOCKPIT is no longer supported and it was only available on Solaris Sparc, HP-UX and AIX. Let's hope that the Alarm-Feature will return in 10.42 or so Gerd "HUGO PADILLA" <hugo_padilla@terra.com.mx> schrieb am 03.03.05 16:13:31: > > Hi there > > You can use cockpit, it is an excellent tool for monitoring the database, I used to work with it, lamentably no longer it exists for version 9.3 > > To use it, first you have to set the environment variable DISPLAY=:0.0 (if you use solaris) where :0.0 is the name of the X server in informix > > Also you have to give permissions with xhosts + (as root) > > Then you have to run the daemon (as informix) > > onprobe service servicename > > Finally you can run the cockpit client (as informix) > > oncocpit service servicename > > ______________________________________________________________ Verschicken Sie romantische, coole und witzige Bilder per SMS! Jetzt bei WEB.DE FreeMail: http://f.web.de/?mc=021193
welllll... I hate it when people are anal - especially me. :0.0 if you are running oncockpit on the machine on which the xterminal is situated - otherwise ip_addres:0.0 the 'xhosts +' has to be issued by the login that owns the x-session where you want the windows displayed. Certainly if you've logged in as root and then su'ed to Informix you would have to xhost by root. But if you logged in as 'jdoe' to the x-session, then jdoe would more normally issue the xhost. Finally, you do not have to xhost the entire world (xhost +) you can specify a machine to xhost (xhost machine +). Otherwise right on the money (ok, cockpit has a 'k' in it). j. ----- Original Message ----- From: "HUGO PADILLA" <hugo_padilla@terra.com.mx> To: <ids@iiug.org> Sent: Thursday, March 03, 2005 10:52 AM Subject: Re: Re: how to know the session [4390] > Hi there > > You can use cockpit, it is an excellent tool for monitoring the database, I used to work with it, lamentably no longer it exists for version 9.3 > > To use it, first you have to set the environment variable DISPLAY=:0.0 (if you use solaris) where :0.0 is the name of the X server in informix > > Also you have to give permissions with xhosts + (as root) > > Then you have to run the daemon (as informix) > > onprobe -service servicename > > Finally you can run the cockpit client (as informix) > > oncocpit -service servicename > >