Path: utzoo!censor!geac!torsqnt!jarvis.csri.toronto.edu!cs.utexas.edu!rice!sun-spots-request
From: medin@cincsac.arc.nasa.gov (Milo S. Medin)
Newsgroups: comp.sys.sun
Subject: Re: SunOS 4.0.3 telnet problems
Keywords: Networks
Message-ID: <5297@brazos.Rice.edu>
Date: 24 Feb 90 08:04:13 GMT
Sender: root@rice.edu
Organization: Sun-Spots
Lines: 16
Approved: Sun-Spots@rice.edu
X-Refs:  Original: v9n46
X-Sun-Spots-Digest: Volume 9, Issue 61, message 7

I don't think your problem is in in.telnetd.  We had the same problem
here.  It turned out to be /bin/login hanging.  If you see a /bin/login -h
hostname -p hanging around the same ptys that the telnetd is attached to,
you have the problem I am talking about.

The cause is that inetd was manually restarted from a shell, and thus
inherited the environment of it's parent process.  It's this environment
that causes things to wedge, because the -p flag to login tells it to
preserve the environment, and the environment that it inherits from inetd
screws it up.  Rebooting the system creates a fresh inetd, minus the
contaminating environment.  SUN knows about this, and it's fixed in 4.1,
due out soon.  I forget the bug #, but if you tell this to your system
support people, they can probably get it from SUN.

						Thanks,
						   Milo