On Wed, 21 Nov 2001, Paul Lustgraaf wrote:
> I just updated from Cricket 0.72 to 1.03 to try to eliminate a problem
> I've been having on a Cisco 3548 48 port switch. In short, the collector
> gets interfaces 1 through 19, then skips to interface 32.
Weird. Didn't see that behavior before.
> In my reading of the code, I am convinced that there are places where
> it uses "defined" on a hash key where it should be using "exists".
Yes, there will be mistakes of this kind. That said, Cricket code does
not have the habit of using undefined entries in a hash, so if it were
to make a difference I'd expect something else to be broken.
We'll be pleased to incorporate such fixes in a future release (or even,
if you can convince us that there is a real problem, to put out an
official patch). I'm curious to know what could be causing the behavior
you are seeing. You are using interface mapping for this device,
> Has anyone else seen similar behaviour?
> I'm using perl 5.00503 if it makes any difference.
I'm using the same and didn't notice it.
Bert Driehuis -- driehuis@... -- +31-20-3116119
If the only tool you've got is an axe, every problem looks like fun!