Undo setrlimit patch for 2.1.3

[Cristian Gafton]

On Sun, 23 Jan 2000, H . J . Lu wrote:

> I know. That has been true for glibc 2.0, 2.1, 2.1.1, and 2.1.2. It
> will be true for 2.1.3 and 2.2. Everytime when we introduce a new
> symbol version, it will happen. Removing the setrlimit change won't
> help you on that since there are many other symbols using GLIBC_2.1.3.

How about this: I recompiled the whole Red Hat distribution against glibc
2.1.3 with the setrlimit changes. There are dependencies introduced in
some binaries for glibc 2.1.3 now. Of all the dependencies, 100% (like in
*all* of them) are dues to the setrlimit change).

I know there are other changes; I know people using explicitly the new
functions will bite it anyway. I know setrlimit is not that different from
that case. But it has a huge potential to cause more pain than be usefull.

Cristian
--
----------------------------------------------------------------------
Cristian Gafton     --     gafton@redhat.com      --     Red Hat, Inc.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  "How could this be a problem in a country where we have Intel and 
   Microsoft?"  --Al Gore on Y2K