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

Bug 52198

Summary:	in.telnetd errors on getpeername socket operation on non-socket
Product:	[Retired] Red Hat Linux	Reporter:	Bret Frohwein <sfbret>
Component:	telnet	Assignee:	Harald Hoyer <harald>
Status:	CLOSED NOTABUG	QA Contact:	David Lawrence <dkl>
Severity:	low	Docs Contact:
Priority:	medium
Version:	7.1	CC:	pekkas
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:	2001-08-28 16:39:33 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 Bret Frohwein 2001-08-21 17:29:12 UTC

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

Description of problem:
when trying to invoke the telnet daemon (vers server-17.10-i386 and server-
17.18) returns with error in.telnetd:getpeername:socket operation on non-
socket.  the daemon will however, run in debug mode and accept connections 
while running in debug mode. This is happening on 5 different machines off 
the cd install.

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


How reproducible:
Always

Steps to Reproduce:
1.signed on the console as root execute /usr/sbin/in.telnetd
2.
3.
	

Actual Results:  in.telnetd: getpeername: socket operation on non-socket

Expected Results:  the daemon should have started

Additional info:

I've poked around a few of the config files to make sure telnet was setup 
in services, etc.. nothing has been added to these servers and 
reinstalling with defaults isn't solving the problem.

Comment 1 Bret Frohwein 2001-08-28 16:38:04 UTC

I've managed to clear up 3/4 of my problem.. sifting through the white papers I 
found an article which stated that I should type, "chkconfig telnet on" then 
issue a reset to xinetd and telnet spawns now when you try to open a session.  
Also I've now installed RH Linux 7.1 on additional machines.  This problem 
seems to ONLY happen on Compaq Deskpro EN desktop machines.  These are new 
machines (as of July)..  Hope this is helpful.   Bret

Comment 2 Bret Frohwein 2001-08-28 16:39:29 UTC

forgot to note that trying to maunally start telnet I still receive the socket 
errors..

Comment 3 Pekka Savola 2001-09-06 07:27:52 UTC

You were trying to run telnetd directly, not through (x)inetd as it should, thus
the error.

I think the desktop, where it still isn't working, isn't running it properly
from xinetd either.

Marking NOTABUG.  If you still can't get it to work, please post
/etc/xinet.d/telnet settings and what you get in /var/log/messages when
restarting xinetd (at least).