Re: {bb} stop sending page messages from client ?

[John Foley <john.foley@motorola.com>]

Philip -

thanks for the reply - your points on the changes and
documentation are well taken; I understand what you're
saying. I will try the BBPAGE modification tomorrow and
see what happens. I thought I had tried something
similar earlier today, but I'll check this again
tomorrow.

I'd still like to know (for my understanding) *where*
the actual page message is created - I haven't been
able to find it anywhere on the client.

My notification requirements are somewhat unique, so I'm
going to "roll my own" notification script, and I
want to make sure that there's no interference from the
"standard" notification system - to insure this, I want
to try to eliminate all the page messages. Interestingly
enough, the windows client has a simple switch on the
config app to turn off all page messages, but the unix
does not appear to be so straightfoward.

Jim -

I've always used the same machine for the DISPLAY and
PAGER too, but the system allows them to be on separate
machines if required (as a matter of fact, you don't
even need a DISPLAY node if all you want is "paging").

      John


Philip Clark wrote:
> On Wed, 2005-12-07 at 22:30, John Foley wrote:
>
> > I'm running the version 1.9c binaries.
> >
> > My understanding is that the client sends the "status"
> > messages to the BBDISPLAY machine, and the "page" messages
> > to the BBPAGER machine - is that not correct ?
>
>
> Yes (or should that be no), that is correct :)
>
> I'd suggest that, if you just want to stop alerts from some
> of your hosts, you should configure bbwarnrules.cfg on the
> server to ignore them. If you really do want the "page"
> message to be stopped, I think that you'll need to modify
> src/bbinc.sh on the client. About three-quarters of the
> way into the file, set BBPAGE to a null value in two places,
> like so:
>
>   BBPAGERS=`echo $BBPAGERS`
>   set $BBPAGERS
>   if test "$#" -eq 1
>   then
>     BBPAGE=""             # ORIGINAL FLAVOR...
>     BBPAGERS=""
>   else
>     BBPAGE=""             # DUMMY - DON'T USE...
>   fi
>
> Caveat - Despite the priorities of many users, sending out
> alerts is really the primary notification function of BB. 
> The web display is essentially there so that you can find
> out why you received an alert.
>
> As a result, configuring a client to never send out a "page"
> message is a lot more non-standard than it may appear and
> could be very difficult to debug if you (or worse, someone
> else) wants to reverse this at a later date. If you do this,
> document it all over the place (e.g. a file called
> WHY_THIS_CLIENT_WONT_SEND_ALERTS.txt on the client. If this
> is just for a sub-set of hosts, I'd be inclined to display
> them on their own web page with a title like "Clients
> Configured Not To Talk To BBPAGER".
>
> Cheers, Phil.

--
########################################################################
# John Foley                       # Maildrop: IL02 - Room EA 900      #
# IT & Systems Administration      #    Email: john.foley@motorola.com #
# Applied Technology Department    #    Phone: (847) 576-8719          #
# Motorola, Inc.                   #      Fax: (847) 576-6521          #
# 1301 East Algonquin Rd.          #     Cell: (847) 344-3026 (Nextel) #
# Schaumburg, Illinois 60196 (USA) #    Pager: (877) 240-2724 (Skytel) #
########################################################################
                (this email sent using Mozilla on VPC)
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=
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.