RE: {bb} Monitor procs by owner?

["Ruork, Robert" <RRuork@tusc.com.au>]

Urs, 

It's a bit more complicated than that, if you want BB to work for you.

My customer's servers are configured with duplicated environments and typically only one user environment is used for production at any time - e.g., processes running as user "uel" are used for development and training, and the "uel2" user processes are the critical production processes. 

A failure in the production environment would not trigger an alarm if the development environment were active due to the same process running in both user environments. 

The ability to identify an active process by both proc name and user ID was accomplished through the configuration of a special process monitoring script (in addition to the BB default process monitoring test), "bb-userproc.sh".

A parameter file "bb-userproctab" was employed to permit this functionality through the use of specific syntax and keywords as shown here:
Keywords:

USER=		can set to specific user to be running a process 
		multiple users can be specified by either USER="a|b" or USER=a USER=b
!USER=		can set to specific user to not be running a process
PID_VALUE=	search for a particular process ID value
		multiple pids can be specified similar to USER= syntax
PID_FILE=	can specify a container file containing mutliple process IDs
		the file contain multiple pids in format of one pid per line or
		pid1|pid2 format. Can only specify one pid file per PID_FILE=
		(i.e. PID_FILE="file1|file2" is illegal - you can use 
		PID_FILE=file1 PID_FILE2
MAX=		specify maximum number of processes
MIN=		specify minimum number of processes
CNT=		specify exact number of processes
"#"		the comment symbol can be used to affix a comment at the end of
		the rule that will be sent with the rule in the verbose status file

Find here sample output of the bb-userproc.sh script:


DBService USER=uel MIN=3 - 3 running   Status: UP
DDService USER=uel - 1 running         Status: UP
LogService USER=uel - 1 running        Status: UP
MBDBService USER=uel - 1 running       Status: UP
MTService USER=uel - 1 running         Status: UP
ODService USER=uel - 1 running         Status: UP
SMService USER=uel - 1 running         Status: UP
SRSService USER=uel - 1 running        Status: UP
TCDBService USER=uel - 1 running       Status: UP
TRTIService USER=uel - 1 running       Status: UP

Again, check deadcat for the script, it is very useful in such circumstanceas as described herein.

Robert Ruork
-------------------------------------------------------------
TUSC Computer Systems Pty Ltd	   Ph: (03) 9840 4426
666 Doncaster Road               Mob: 0419 840 410
DONCASTER Vic 3108 Australia	   Fax: +61 (03) 9840 2277 
web: http://www.tusc.com.au	   mailto:rruork@tusc.com.au
-------------------------------------------------------------


-----Original Message-----
From: Urs Krolzig [mailto:urs.krolzig@bluewin.ch]
Sent: Thursday, 2 December 2004 6:12 AM
To: bb@bb4.com
Subject: Re: {bb} Monitor procs by owner?


Isn't it ps -fu <username>

regards urs
----- Original Message ----- 
From: <Kevin.Hanrahan@novainfo.com>
To: <bb@bb4.com>
Sent: Tuesday, November 30, 2004 10:58 PM
Subject: {bb} Monitor procs by owner?


> Does anyone know of a way to monitor processes on a unix system (solaris
> here) by process owner instead of by process name?
>
> Kevin
>
> Note:  The information contained in this email and in any attachments is
> intended only for the person or entity to which it is addressed and may
> contain confidential and/or privileged material.  Any review,
> retransmission, dissemination or other use of, or taking of any action in
> reliance upon, this information by persons or entities other than the
> intended recipient is prohibited.  The recipient should check this email 
> and
> any attachments for the presence of viruses.  Sender accepts no liability
> for any damages caused by any virus transmitted by this email. If you have
> received this email in error, please notify us immediately by replying to
> the message and delete the email from your computer.  This e-mail is and 
> any
> response to it will be unencrypted and, therefore, potentially unsecure.
> Thank you.  NOVA Information Systems, Inc.
> --
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=
> To unsubscribe from this list, or to subscribe to the bb-digest list
> send e-mail to mailto:majordomo@bb4.com with unsubscribe bb -and/or-
> subscribe bb-digest in the BODY of the message. 

--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=
To unsubscribe from this list, or to subscribe to the bb-digest list
send e-mail to mailto:majordomo@bb4.com with unsubscribe bb -and/or-
subscribe bb-digest in the BODY of the message.

--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=
To unsubscribe from this list, or to subscribe to the bb-digest list
send e-mail to mailto:majordomo@bb4.com with unsubscribe bb -and/or-
subscribe bb-digest in the BODY of the message.