I hope this is the right forum to inform about in bug in glibc-2.1.1.
Otherwise please tell me where to go. (I don't know the adress of a
glibc mailing list).
We just ported our very large ERP system to linux. All went well but
the programs were very slow.
After 3 days of bug hunting I observed that our debugging package uses
sleep(0) very often. In all OSes we already used this makes no
problem. But glibc-2.1.1 uses nanosleep() to implement sleep(). A call
of nanosleep to sleep for 0 seconds results in a sleep of at least
10ms (as also described in the manual page).
We think this is a bug. sleep() should check for a argument of 0 and
simply return in this case.
glibc-2.0.7 doesn't have this problem, because this version does not
use nanosleep() to imlement sleep().
This bug is currently no problem for us any longer. We simply check
ourselves for a 0 argument to sleep. But it might happen that other
people also run into this same problem.