Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!tut.cis.ohio-state.edu!ucbvax!hplabs!hpfcso!hpfcmgw!rocky
From: rocky@hpfcmgw.HP.COM (Rocky Craig)
Newsgroups: comp.sys.hp
Subject: Re: telnet and getty questions
Message-ID: <1080127@hpfcmgw.HP.COM>
Date: 9 Feb 90 05:38:10 GMT
References: <16390@boulder.Colorado.EDU>
Organization: HP Fort Collins, CO
Lines: 24

> Then, rlogin <my-host-name>
> the /etc/issue message gets printed and then I get my prompt back (i.e. the
> exec doesn't happen).

> I did exactly the same thing with the telnetd and the /etc/issue message 
> gets printed and the login prompt appears.

> Any ideas?

Yeah, don't listen to yahoos who come up with quick fixes at 4:30 a.m. :-)

I tried it, got your results, THEN read the man page /o\.  Look in the 
"Diagnostic" section.  Both rlogin/rlogind and telnet/telnetd appear
to hold a "connection established" dialogue before running login(1M).
Apparently the rlogin/telnet running locally is interpreting the
contents of /etc/issue as a "connection failed" message and terminating.

You probably don't want to replace your login(1M) with a front end...
I guess if you REALLY wanted this, you could write your own socket-based
front end that fired up a....Nahhhhhhhh.

Sorry about the bad advice, but it sounded good the other morning :-)

Rocky "No advice in this note, so no disclaimer needed" Craig