Bug 103392
Summary: | application hangs during call to syslog | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Erik Horn <erik_horn> |
Component: | glibc | Assignee: | Jakub Jelinek <jakub> |
Status: | CLOSED NOTABUG | QA Contact: | Brian Brock <bbrock> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 9 | CC: | fweimer |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2003-11-05 18:56:58 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
Erik Horn
2003-08-29 18:08:13 UTC
The problem appears to be associated with re-entrant calls to syslog. One person who was having serious problems with this, downgraded their system to redhat 8 and the problem went away. The problem may not be with the redhat release, but it seems quite suspicious. I suspect problems with the use of syslog. It does locking, yes, but that locking cannot deadlock by itself. Does the program use threads? Does it use fork? If yes, how is fork used, I mean, which functions are called after fork? No response in a month. I see no reason to believe that glibc has a bug here. Closing. |