The main problem was that threads would die, but I found no reliable way of detecting this. Also, some advice I found on the web said that you shouldn't create too many threads - they weren't designed for that. However, there was no mention of what the limit might be, how to determine the limit, or how to discover whether thread creation succeeded or failed. All this means that if you want to create a couple of threads, it should (?) work, but beyond that, who knows?
At 04:07 PM 7/29/2004, Nadjaf Kuliev wrote:
When i tested my IIS vulnerability checker, it works perfecly, but when I added multitasking support, it starts good, bit by bit cpu noise increases then perl crases with unknown error. I didnt use fork(). I used builtin Threads support with async{}. I dont want to make the code public before first release so ill tell some details, if it wont help i will email some of you who really wants to help the code. So here it is, the main scripts gets all the vulnerability check, ie vulnerable file checks from a file and tries them one by one on particular IIS webserver. Ony by one is really slow, so I implemented threads. As you may know if it is checking the webserver it surely will send HTTP requests for each vulnerable file. I use IO::Socket only, not HTTP support modules.
As far as i can guess, the reason for crash is most probably not in the code but in the perl, perl threads support particularly and how interacts with my OS - windows 98.
Any help is greatly appreciated. Thanks in advance.
Respect, OkIDaN. _______________________________________________ Perl-Win32-Users mailing list [EMAIL PROTECTED] To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
_______________________________________________ Perl-Win32-Users mailing list [EMAIL PROTECTED] To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
