One of the machines that I scan has decided that it would like to loop after being scanned by Nessus. Since the looping process is not something standard, I have to discover which of the 220 or so tests that I have configured is causing this. I thought I could do this by setting 'delay_between_tests = 120' or something like that so that only one test every two minutes would be launched and we could then compare timestamps between scanning and scanned machines to find out which plugin it is that causes this loop.
Unfortunately, it appears that this parameter doesn't do what it suggests since even with it set to 12000, the entire test set is complete in 34 seconds :-( Does anyone have any alternative debugging methods I can use instead of this? What's happening is that one of the tests I have configured causes one of the web processes on the machine that is being scanned to loop. It then loops until it's shutdown and restarted. I don't want to run through all 220+ tests manually running them with nasl -t etc since I suspect that they might not all work in any case. Trevor Hemsley, Security Specialist, Atos Origin Ltd, Whyteleafe, +44-(0)1883-628139 [This e-mail and the documents attached are confidential and intended solely for the addressee ; it may also be privileged . If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on internet, the Atos Origin group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.] _______________________________________________ Nessus mailing list [EMAIL PROTECTED] http://mail.nessus.org/mailman/listinfo/nessus
