[NETFRAME] Net::Packet::Dump / Net::Frame::Dump::Online - Concurrent Simultaneous Capture Limit?

[Darien Kindlund]

Hi GomoR,

I just discovered this mailing list, so I thought I'd post my original
question here, with more detail.  I'd like to know if you've ever
tried to run multiple Net::Packet::Dump or Net::Frame::Dump::Online
instances, within a single parent Perl process.  Specifically, have
you ever encountered problems with running upwards of 20+ of these
Dump instances simultaneously?

Additionally, do you know if it's okay to quickly call ->start(), then
->stop(), then ->clean() in rapid succession (within 10s of each
other) repeatedly on the same Net::Packet::Dump?  How about the
equivalent of ->start(), then ->stop(), then ->flush() in rapid
succession for Net::Frame::Dump::Online?

Lastly, at least with Net::Packet::Dump, it seems that when I call
->start(), then ->stop(), then ->clean(), the forked "tcpdump" process
ends and creates a new fork during the next iteration.  One of the
side effects appears to be that when the child process dies, DESTROY
calls were getting activated in the parent process -- even though the
parent process is still alive.  I didn't know if you've encountered
this problem before.

If it would help, I can try to provide some example code, which
further describes these situations.

-- Darien