Ok, so glibc version is 2.3.2 with some Mandrake specific patches, with (according to the indications in the sources) linuxthreads 0.7 included. Florin
On Tue, 2005-04-05 at 00:02, Burton Strauss wrote: > It's possible - sort of, and in some situations - to figure out which thread > library is being used and what the version of glibc is. > > The question then becomes whether we can use this information to avoid the > syslog() wrapping mutex calls if we KNOW that we don't need them. > > 1. The default (including unkown information case) needs to be to use the > mutex() calls. > > 2. We need to identify the specific case(es) which we know are safe. And do > it in such a way that when ntop hits something new, it will handle it > properly. > > > I see a couple of alternatives. > > 1. Reverse the meaning of the -D flag and require explicitly it be present > in configureextra/ files where we know we can skip the calls, e.g. FC2/3. > > 2. Do some sort of run-time testing. > > > > Thoughts? > > -----Burton > > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf > Of Florin > Sent: Monday, April 04, 2005 2:59 PM > To: [email protected] > Subject: Re: [Ntop-dev] 3.1 Hang Info (was: SMP linux hangs with ntop) > > Did the ntop part of the hacking and it seems to work, except that it uses > 99% of CPU 1 (well, kinda, since it's still Pentium 4 HT ). > Concerning the glibc bug, it seems having been fixed in Mandrake 9.2 in a > personal way (the patch is present but modified). > <snip /> > > > _______________________________________________ > Ntop-dev mailing list > [email protected] > http://listgateway.unipi.it/mailman/listinfo/ntop-dev _______________________________________________ Ntop-dev mailing list [email protected] http://listgateway.unipi.it/mailman/listinfo/ntop-dev
