Is there some way within Scotty that I can validate
the health of the straps-scotty connection?
I could do heartbeats from within the Scotty session,
but that feels very ugly.
My application in fact does not expose the Scotty
interpreter, but if I understand a solution for this
situation, I'm confident I can generalize it.
2. Imagine, again, that we have a host where straps
instances are coming and going. Sometimes when I
try to bind a trap-handler, Scotty reports "can not
connect straps socket: broken pipe". Immediately
afterward, binding is successful.
I have a customer who reports some of the same, with
a "broken plate" message (!?).
What's the story? Is this one of those LINGERing
sockets?
I confess, I haven't looked through much of the source code. I
know sockets well enough that I'm confident I could unravel
whatever is going on. I'm hoping to save myself some of the
work, and also learn what others are doing to cope with these
exceptions.
Cameron Laird http://starbase.neosoft.com/~bodi/nesi.html
Network Engineered Solutions +1 713 763 8366
claird@NeoSoft.com +1 281 996 8546 FAX
Houston WWW Business Guide: http://starbase.neosoft.com/~bodi/HouGuide.html
-- !! This message is brought to you via the `tkined & scotty' mailing list. !! Please do not reply to this message to unsubscribe. To subscribe or !! unsubscribe, send a mail message to <tkined-request@ibr.cs.tu-bs.de>. !! See http://wwwsnmp.cs.utwente.nl/~schoenw/scotty/ for more information.