Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 4107 - Problems with threads under RH 6.0
Problems with threads under RH 6.0
Product: Red Hat Linux
Classification: Retired
Component: glibc (Show other bugs)
sparc Linux
medium Severity medium
: ---
: ---
Assigned To: Cristian Gafton
Depends On:
  Show dependency treegraph
Reported: 1999-07-19 01:23 EDT by josh
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 1999-07-28 02:15:08 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description josh 1999-07-19 01:23:41 EDT
MySQL has problems creating threads under RH 6.0 due to
what looks like a glibc2 bug. This is actually a regression
to a bug in an earlier release of RH.

If you compile MySQL and then try to run safe_mysqld, it
looks like everything works fine until you take a look and
see that only one MySQL process/thread is running when in
fact three threads are supposed to be created upon MySQL
startup. As a result, the mysqld daemon is useless. It does
not create its unix socket nor does it listen on port 3306
as it's supposed to.

When I had this problem on RH 5.1, upgrading to the latest
glibc libraries fixed the problem. After upgrading to RH
6.0, the problem is back again.

Note that this is on a sun4c workstation (SPARCstation 2).

I don't know whether the regression occured at GNU or at
RedHat, so I'm submitting it here for you to figure out. :)
Comment 1 Cristian Gafton 1999-07-28 02:15:59 EDT
Is the problem still experienced with glibc-2.1.2-1 and later?

Please reopen if the problem still persists.

Note You need to log in before you can comment on or make changes to this bug.