That's cool. I wrote a script called easy-creds. Then when the new kernel came out for BT5R1 (2.6.39-4) I noticed the Send L3 errors going like crazy. Everything still works, but man were those errors annoying. So one of my friends fixed it. Then I e-mailed Alor and told him we wanted to take over official ettercap development. Incredibly, he granted us project admin status. Since then we've been going crazy try to fix all the bugs, etc.
We're planning a 1.0 release for July. If you're interested in development or testing, please let me know. On twitter I'm Brav0Hax and in irc I'm J0hnnyBrav0 Best Regards, Eric Milam Senior Security Assessor Accuvant Labs [email protected] Cell: 925-783-2773 Corp: 303-298-0600 -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of LocutusOfBorg Sent: Monday, November 28, 2011 10:22 PM To: Eric Milam Subject: Re: [Bug 817101] Re: ettercap produces Error 11 and runs out of resources Actually I'm not in the ettercap source mantainers group... :) I just manage here on launchpad to make things work and sometimes foward patches upstream, I'm LocutusOfBorg on git and I'm a watcher now... Does the project needs upstream help? ** Changed in: ettercap (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/817101 Title: ettercap produces Error 11 and runs out of resources Status in “ettercap” package in Ubuntu: Fix Released Bug description: OS: Ubuntu 10.04 2GB RAM 2 Processors (Is patched with the latest updated from the repos) Issue: I was poisoning 22 victims, ettercap lasted roughly 10 minutes before it closed with the following message: ERROR : 11, Resource temporarily unavailable [ec_threads.c:ec_thread_new:203] not enough resources to create a new thread in this process I found this in my research, apparently its from the Ettercap forums/bug list from 2004: "It's a known issue because pthread_exit seems to not free correctly threads' memory. We are investigating this problem." My etter.conf has the ec_uid & gid set to 0 and the proper iptables redirs uncommented. I have experienced this issue with ettercap installs from both the Ubuntu repos & compiling from source. ulimit is set to unlimited: root@blank:~# ulimit -Ha core file size (blocks, -c) unlimited data seg size (kbytes, -d) unlimited scheduling priority (-e) 20 file size (blocks, -f) unlimited pending signals (-i) 16382 max locked memory (kbytes, -l) 64 max memory size (kbytes, -m) unlimited open files (-n) 1024 pipe size (512 bytes, -p) 8 POSIX message queues (bytes, -q) 819200 real-time priority (-r) 0 stack size (kbytes, -s) unlimited cpu time (seconds, -t) unlimited max user processes (-u) unlimited virtual memory (kbytes, -v) unlimited file locks (-x) unlimited As a workaround I set my max threads to 123,456,789 up from 39K. It still ran out of resources after about 15 minutes. I am not a developer, but in reading up on pthreads, it looks like you have to specify "joinable" if you use pthread_join and the code does not appear to do this. However, I know nothing about pthreads and am still learning the basics of C. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ettercap/+bug/817101/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/817101 Title: ettercap produces Error 11 and runs out of resources To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ettercap/+bug/817101/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
