Path: utzoo!attcan!sobmips!uunet!samsung!shadooby!mailrus!purdue!decwrl!shelby!portia!forel!karish
From: karish@forel.stanford.edu (Chuck Karish)
Newsgroups: comp.sys.ibm.pc.rt
Subject: Re: TCP/IP, telnet and the RT...
Message-ID: <6706@portia.Stanford.EDU>
Date: 16 Nov 89 13:37:50 GMT
References: <16994@uhnix1.uh.edu> <605@ursa-major.SPDCC.COM> <6680@portia.Stanford.EDU> <610@ursa-major.SPDCC.COM>
Sender: USENET News System <news@Portia.stanford.edu>
Reply-To: karish@forel.stanford.edu (Chuck Karish)
Distribution: na
Organization: Mindcraft, Inc.
Lines: 27

In article <610@ursa-major.SPDCC.COM> dyer@ursa-major.spdcc.COM
(Steve Dyer) wrote:
>In article <6680@portia.Stanford.EDU> karish@forel.stanford.edu
(Chuck Karish) writes:
>>Or else the ptys are present, but none are enabled.  Use `devices' to
>>turn the `ae' (auto-enable) option on for some of the ptys, so getty
>>will listen for logins on them.  Some un-enabled ptys should also be
>>present, for outgoing telnet and ftp sessions.
>
>Are you telling me that AIX/RT doesn't use inetd but instead requires
>getty to be spawned and waiting on each pty??  Gad.  At least AIX PS/2
>gets THAT right.

I don't know precisely how this all works.  AIX/RT doesn't run a getty
for each pty.  It seems to keep a pool of gettys available, and inetd
associates them with ptys as requested.  The documentation for
setting up TCP/IP told me to make some ptys with ae set and some
without, so I did it and it worked.  It said that it used separate
ptys for the different streams FTP uses (2.1.1 doc).

AIX PS/2 also has two types of ptys, one with logins enabled and
one not.  It seems to set up ptys the same way the RT documentation
told me to.  The difference is that more of the configuration is
pre-set in the configuration files used by `devices'.

	Chuck Karish		karish@mindcraft.com
	(415) 323-9000		karish@forel.stanford.edu