Re: {bb} Multiple instances of bbd?

["Eric Frisch" <ericf@conetra.com>]

>
>Is it possible to have several instances of bbd running on a single BB
>server?


Yes

>
>My company has some strange requirements for paging.  I have a couple Sun
>servers where the database failures need to page the Oracle admins, and the
>rest of the system needs to page the Sun admins (and other such nonsense).


The BBWARN type notification is better for this than separate instances.  I
set up multiple instances to have different status screens for different
departments and separate paging before BBWARN integration.  If you want a
high degree of separation like this then go down this road but minor
customization is required.

>I'm thinking maybe 4-5 instances of bbd on ports 1984, 1985, 1986, &c. (one
>for each group), and a couple different runbb.sh scripts running on the
>monitored clients pointing to the appropriate port.


This works, notes of interest:

1) Rename the bbd and bb_run.sh to something like bbd_instance1 and
bb_run_instance1.sh and create separate rc startup/shutdown scripts for each
one.  Life is confusing if you don't do this.
2) You must configure the instances to share the same paging lock area or
there will be conflicts.  Extract from my bbsys.sh,
PAGINGLOCK=${BBTMP}/../../tmp/paginglock.  This assumes a common hierarchy
bb/instance1/..., bb/instance2/... and bb/tmp etc.  Don't rely on the OS
lock files for the serial ports that are also referenced it the code, I
found these to be wrong in some cases, Solaris 2.6 comes to mind.

>
>Has anyone done this?

>

Yes, but as stated above BBWARN notification is the path of least resistance
. . .

Eric Frisch


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  Please send mail for the mailing list to: bb@taex001.tamu.edu
  To [un]subscribe to this list, send e-mail to majordomo@taex001.tamu.edu
     with [un]subscribe bb in the BODY of the message.
  Please contact the mailing-list-owner as: bb-owner@taex001.tamu.edu