As I should have done to start with, I went back and put a little debug line in my script within the sub, and as you suspected, it's running the sub, but NOT executing all the way through like it was when I wasn't forking it with this module (pun intended). The sub is supposed to kick off several nmap scans, save the output to different files per network, etc. and it simply isn't doing it. The issue ISN'T what I thought it was.. for some reason, it appears the fork mgr runs the parts of the sub it feels like running, and chunks the rest.. I have it set to do 8 threads, and each thread should take a while, but it rips through a list of 20 networks instantly, prints them all out, and does nothing further, so I guess I gotta figure out what's different.
I appreciate your help.
UPDATE:
Well, as it turns out, I had hosed the path to nmap in my subroutine, and Perl wasn't telling me. I'm thinking I GOTTA learn how to use the debugger.
Comment on Re^4: Calling a sub routine from an object
I'm thinking that instead of a debugger, you should probably be checking return values from something. If your program called nmap directly, did it also check the exit status from nmap to make sure it worked properly?
Debuggers are useful, yes, but more important is writing code to tell you what goes wrong when something does go wrong.