On Saturday 05 February 2005 02:01, Gary Smith wrote: > Quoting Nick Warne <[EMAIL PROTECTED]>: > > Here is the link that explains it... what to do with many processes > > segfaulting, I don't know. RHEL support is _very_ good - give them a > > ring. > > > > http://people.redhat.com/drepper/assumekernel.html > > > > Nick > > Nick, > > The article seems to make sense about the versioning. I was wondering what > your resolution was.
I run two boxes in the UK with RHEL 3 for DNS/DHCP running Lucent's QIP/QMS services (Montreal admins run that). All I am is local SysAdmin on all the other stuff. When I up2dated GLIBC the only thing that went wonky at first was smartmontools (built from src), everything else appeared OK. About 4 days later, I was asked to check why one of the QIP monitoring tools wasn't running (it's a JVM thing, precompiled binaries). I then called the Montreal Linux guy, and he sussed it and told me it was the assume_kernel problem. As it is their area, I never asked what he done exactly to fix it, but he did say that although the GLIBC upgrade broke the tool, once he fixed the problem, it was now working correctly using pthreads (or something) that it wouldn't use before the upgrade. I will ask for more info Monday when back at work. I think Barry K. Nathan reason/problem/solution looks more likely though, re futex in this thread. Nick -- "When you're chewing on life's gristle, Don't grumble, Give a whistle..." - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
