Re: [Devmon] Little problem with devmon

[Schwimmer, E. E *H. <EE...@hs...>]

> > > 2) do a bb $bbdisplay "query $hostname.conn" before polling each
> > > device and if the result is not "green" send clear as
> > status for each
> > > test of that device (so they'll not become purple or start to
alert
> > > everyone because a router is down...
> > > It will also solve problem when a router before your router is
down
> > > because it will be the only one reporting the error if you
> > configured
> > > the routing)
> >
> > As above.  This would require having the bb client installed
> > on the devmon system, as well as making a shell call out to
> > it (I try to avoid making shell calls, since they are
> > expensive).  I've tried getting two-way communication going
> > between devmon and hobbit in the past, but I've been defeated
> > by some weirdness in perl's IO::Socket routines (I can get
> > the client to send or receive, but not both.  However, I've
> > written a C client that works fine.  Go figure).  I'll poke
> > at my two-way communication some more, maybe I'm not not
> > flushing a buffer properly, or something.
>=20
> It's interesting to get the host status just to avoid to try to get
data
> from a dead host that probably have to wait for SNMP to timeout.
>=20

I've got this done, but not yet debugged.  I ended up using
'hobbitdboard test=3Dconn field=3Dhostname,color" instead of "query", as =
it
allowed me to get all the device status in one easy to parse message. =20

I haven't tested it yet; that's next week :)

FYI, in case anyone is curious, the reason I wasn't able to get
bidirectional comm working with hobbit is that hobbit expects you to
close your client socket's write descriptor before you can read.=20

-Eric