Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 55841

Summary:	Xinetd shuts down when screen blanks out.
Product:	[Retired] Red Hat Linux	Reporter:	wolfson_curt
Component:	xinetd	Assignee:	Trond Eivind Glomsrxd <teg>
Status:	CLOSED NOTABUG	QA Contact:	Brock Organ <borgan>
Severity:	high	Docs Contact:
Priority:	medium
Version:	7.2
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:	2001-11-07 16:35:47 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 wolfson_curt 2001-11-07 16:35:42 UTC

From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 4.0; RCN042099d)

Description of problem:
My screen blanks then all services including ping, telent smb nmb ftp http 
shuts down. Server becomes unreachable. When I go to check logs the screen 
is either black from blanking or my screen saver is initalized. I turned 
the screen saver off. Waited for the screen to blank and all my services 
went down again. The moment I brought up the screen the services returned.
 

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

How reproducible:
Always

Steps to Reproduce:
1.Turn on all services
2.Wait till screen blanks
3. try ping 
4. hit a key to start services
	

Actual Results:  the system services go down and have to be brought back 
on line manually

Additional info:

Comment 1 Trond Eivind Glomsrxd 2001-11-07 16:40:40 UTC

This doesn't sound like an xinetd problem, but rather the system shutting down
(power save mode?) or similar.

Comment 2 wolfson_curt 2001-11-07 20:22:00 UTC

I setterm -blank 0 to turn off screen blank and tryed to 
setterm -powersave off. This did not fix the problem. I also noticed all 
services on a different subnet shutdown first.
At the same time to prove it wasnt a network issue I had a 6.2 with kernel
2.2.17-14 using vnc to talk to another system on the alternate subnet 
It worked fine. I went over to my 7.2 system kernel 2.4.9-13 the screen 
did not blank. I hit a key and services came back.
The processor in the 7.2 is a intel pentium 230, the lan is a eepro100, scsi is
aic7xxx and qla2x00