Bug 77773

Summary:	xinetd fails to spawn ipop3
Product:	[Retired] Red Hat Linux	Reporter:	Need Real Name <mark>
Component:	xinetd	Assignee:	Trond Eivind Glomsrxd <teg>
Status:	CLOSED DUPLICATE	QA Contact:	Brock Organ <borgan>
Severity:	high	Docs Contact:
Priority:	medium
Version:	7.2
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-12-03 20:32:02 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-11-13 13:12:22 UTC

Description of Problem:
After a period of use, xinetd fails to spawn the ipop3 process.  telnet on port 
110 gives a connection, but ipop3 is not spawned and so no data is transmitted 
via the connection.

This seems to occur on my not terribly busy server after around a day; I have 
tried repeatedly connecting and disconnecting with telnet to no avail in 
reproducing the problem.

The workaround is simply to restart xinetd.

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

How Reproducible:
Happens daily.

Steps to Reproduce:
1. Leave xinetd for a while
2. connect with telnet
3. watch no process get spawned

Sorry I can't make this greatly repeatable.  I can't find anything else that 
looks like this bug.

Comment 1 Stephen Samuel 2002-12-03 20:31:55 UTC

This appears to be a duplicate of 76146 (87104 also contains a lot of data)
Resolved by errata. 

 http://rhn.redhat.com/errata/RHSA-2002-196.html

Comment 2 Bill Nottingham 2002-12-03 20:35:28 UTC


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