Advanced
Mailing List Archive

Mailing List Archive

  1. Home >
  2. Gentoo>
  3. Dev
glibc-2.7 stabilization
vapier at gentoo
Apr 10, 2008, 12:02 AM
Post #1 of 4 (141 views)
Permalink
some heads up here

glibc-2.7 has sat in ~arch for much longer than i would have liked. the only
real issue holding it back is nscd. i never use this thing myself, but on
some arches (like ppc), it's known to eat your cpu like a dirty C-globbler
(where C is short for CPU). on other arches, it's known to just cream itself
for fun and then promptly exit.

glibc-2.8 is supposed to be out soonish, and if nscd insists on continuing to
be a pile, i'm afraid of having to just dump in a bunch of reverts. nscd in
glibc-2.6.1 seems to be generally OK.
-mike

Attached Files:

Re: glibc-2.7 stabilization [ In reply to ]
yoswink at gentoo
Apr 10, 2008, 7:15 AM
Post #2 of 4 (144 views)
Permalink
Hey Mike:

Mike Frysinger escribió:
> some heads up here
>
> glibc-2.7 has sat in ~arch for much longer than i would have liked. the only
> real issue holding it back is nscd.

In alpha we still have a bastard called 205099[1]. We need to track down
the real problem there and fix it before we can mark 2.7 even ~alpha.
Any help from toolchain ninjas is more than welcome. Thanks.

[1] http://bugs.gentoo.org/show_bug.cgi?id=205099

--
Jose Luis Rivero <yoswink@gentoo.org>
Gentoo/Doc Gentoo/Alpha
--
gentoo-dev@lists.gentoo.org mailing list
Re: glibc-2.7 stabilization [ In reply to ]
vapier at gentoo
Apr 10, 2008, 1:15 PM
Post #3 of 4 (146 views)
Permalink
On Thursday 10 April 2008, José Luis Rivero (yoswink) wrote:
> Mike Frysinger escribió:
> > glibc-2.7 has sat in ~arch for much longer than i would have liked. the
> > only real issue holding it back is nscd.
>
> In alpha we still have a bastard called 205099[1]. We need to track down
> the real problem there and fix it before we can mark 2.7 even ~alpha.
> Any help from toolchain ninjas is more than welcome. Thanks.

as noted, that needs to be fixed in the kernel. working around it in glibc
doesnt make the issue go away. you could even call it a security vuln since
any non-root user can take down the machine.
-mike

Attached Files:

Re: glibc-2.7 stabilization [ In reply to ]
holger at wizards
Jun 17, 2008, 1:29 AM
Post #4 of 4 (138 views)
Permalink
On Thu, 10 Apr 2008 03:02:17 -0400, Mike Frysinger wrote:

> some heads up here
>
> glibc-2.7 has sat in ~arch for much longer than i would have liked. the
> only real issue holding it back is nscd. i never use this thing myself,
> but on some arches (like ppc), it's known to eat your cpu like a dirty
> C-globbler (where C is short for CPU). on other arches, it's known to
> just cream itself for fun and then promptly exit.

Interesting - I saw nscd dying every so often with 2.6 (x86) but at least
for me that seems to have stopped since 2.7. Not sure what I'm doing wrong :)
On slower systems it certainly makes a noticeable difference.

-h


--
gentoo-dev@lists.gentoo.org mailing list

©2024 GT.net. A Gossamer Threads company.
5th Floor, 455 Granville St., Vancouver, BC V6C 1T1, Canada | Legal