Bug 76242

Summary:	mysqld segfaults on remote connections
Product:	[Retired] Red Hat Linux	Reporter:	Need Real Name <spiette>
Component:	glibc	Assignee:	Jakub Jelinek <jakub>
Status:	CLOSED DUPLICATE	QA Contact:	Brian Brock <bbrock>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.2	CC:	fweimer
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2002-10-18 16:17:09 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 Need Real Name 2002-10-18 16:16:54 UTC

Description of Problem:

The new glibc-2.1.3-27 cause the same problem than glibc-2.2.5-40 in RH Linux
7.3 (see bugs 74943, 75290, 75297). It would be nice to have a 2.1.3 patched in
a way that makes possible to get a working and secure glibc AND a working mysql
installation.

Version-Release number of selected component (if applicable):
2.1.3-27

How Reproducible:

get your RH 6.2 installation up to date. Install any 3.23.x release (in my case
it is 3.23.36). Try to log in remotely. 

Actual Results:

mysqld process hanging, pid 11727 - killed
021018 12:10:37  mysqld restarted


Expected Results:
Welcome to the MySQL monitor.


Additional Information:

Comment 1 Jakub Jelinek 2002-10-18 20:21:41 UTC


*** This bug has been marked as a duplicate of 75128 ***