Re: new : iperf servers that stay alive
On Wed, 29 Jan 2003, Kevin Gibbs wrote:
> A supported fix for the problem of "pthread_create failed" after handling
> a lot of clients, is to add the following line:
>
> pthread_detach( mTID );
>
> immediately following line 118 of lib/Thread.cpp which is:
>
> FAIL( err != 0, "pthread_create" );
I still think this change is sufficient only under the assumption that
the remaining pthread_exit() system call is dead code (that should
never be enabled again).
My patch made an additional "inheritance change" in order to be more
flexible and allow future evolutions call pthread_exit() again. But
maybe something I still escaping my understanding of the code ?
Thanks in advance for any explanations!
More details about this in the comments inside my patch.
> The other "problems/bugs" were caused by Marc's changes (and possibly
> fixed as well).
If they were caused by my changes, well... then they surely are fixed
by your fix, since yours does not include mine :-)
More seriously, what where these "other problems" I introduced ? I
hope it did not miss some related message on the list...
Cheers,
Marc.
--
Marc Herbert
Ph.D Intern
SunLabs Europe / INRIA
> On Wed, 22 Jan 2003 Marc.Herbert --at-- ens-lyon.fr wrote:
>
> >
> > On most systems, iperf servers had a limited life expectancy. I think
> > you can bring down most TCP iperf servers using such a loop :
> >
> > n=1; while (./iperf -t 1 -c server.to.crash -P 50 ) ; do printf "\n\nn $n\n\n\n"; let n=$n+1; date; done
> >
> >
> > The heavily commented patch "iperf165_thread.patch"
> > <http://marc.herbert.free.fr/TCP/iperf/>
> > hopefully solves the issue. Any feedback on it is highly welcome
> > (further test results, congratulations, insults,...) It was tested on
> > debian woody linux 2.4.18 and Solaris 2.6.
> >