Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uunet!snorkelwacker!ira.uka.de!smurf!urlichs
From: urlichs@smurf.ira.uka.de
Newsgroups: comp.protocols.appletalk
Subject: Re: Interpoll crashes: followup
Message-ID: <1383@smurf.ira.uka.de>
Date: 13 Jan 90 20:19:01 GMT
References: <354@bnrgate.UUCP>
Reply-To: urlichs@smurf.ira.uka.de (Matthias Urlichs)
Organization: University of Karlsruhe, FRG
Lines: 27

In comp.protocols.appletalk aruigrok@bnr.ca (Adrian C Ruigrok) writes:
< 
< I did a network trace and learned a few things that you may find 
< interesting.  First of all, I did not realize that interpoll did name 
< binding broadcast requests while you were in the network dialog.  It 
< explains why I was crashing even before I started a search.  What 
< interpoll does with the data it is getting in background I can only guess.
< 
When you search for a specific type of entity, InterPoll uses these to make a
pop-up menu listing all the types it found. (This is a really obscure feature
because if you're like me, zipping through these dialogs, you often wonder why
the pop-up menu si empty ;-)

< One of the last packets I received was a NBP Lookup-Reply with one of the 
< entries being node 0.  So does this illegal value of a node number kill 
< Interpoll.
But if you really have a node zero, that's somewhat understandable. That node
number is forbidden by law and/or system crashes. (You experienced these...)

Find out which machine sends such responses, shut it down, and fire the
programmer who caused this kind of behavior.

< Comments?  Other people come across this?  
Fortunately not...

-- 
Matthias Urlichs