Bug 4107

Summary:	Problems with threads under RH 6.0
Product:	[Retired] Red Hat Linux	Reporter:	josh
Component:	glibc	Assignee:	Cristian Gafton <gafton>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.0
Target Milestone:	---
Target Release:	---
Hardware:	sparc
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	1999-07-28 06:15:08 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description josh 1999-07-19 05:23:41 UTC

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 06:15:59 UTC

Is the problem still experienced with glibc-2.1.2-1 and later?

Please reopen if the problem still persists.