Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Occassional failure to close children processes #434
@7a : I noticed that with the w3af “finding buffer overflows in web apps” tests, w3af tends to crash due to lack of memory, OWTF however, appears to fail to close these processes sometimes:
The children process clean-up needs to be revisited to solve this problem.
Dead children processes: root 6671 18701 0 Mar06 ? 00:00:00 /bin/sh -c cd owtf_review/targets/http__some.host.com/partial/W3Af_Unauthenticated/active; /root/owtf_develop/scripts/run_w3af.sh /usr/share/w3af/w3af_console http://some.host.com 127.0.0.1:8008 'Mozilla/5.0 (X11; Linux i686; rv:6.0) Gecko/20100101 Firefox/15.0' root 6672 6671 0 Mar06 ? 00:00:00 bash /root/owtf_develop/scripts/run_w3af.sh /usr/share/w3af/w3af_console http://some.host.com 127.0.0.1:8008 Mozilla/5.0 (X11; Linux i686; rv:6.0) Gecko/20100101 Firefox/15.0 root 6683 6672 88 Mar06 ? 14:39:31 python /usr/share/w3af/w3af_console -n -s w3af_report2015-03-06_22_05_11.script.w3af
I killed the w3af process, and let the OWTF wrapper scripts do their job with the hope of saving some results out of the scraping from w3af despite the crash. All of which was OK running this command (see PIDs above):