telnetd ..help!

QNX Newsgroups (Archives) comp.os.qnx
1

Hello everyone.

I’m trying to integrate telnetd into a embedded PC104-based system with
Neutrino and am having loads of trouble figuring out how to get telnetd to
work so that we can do some basic maintenance work on the embedded system.
I’ve already made the build files and got the ftpd server up and running
fine.
When I try to log into the system from my QNX development PC, I am allowed
to enter the username and password, but upon hitting enter after the
password, I immediately receive the notification “connection closed by
foreign host”
The embedded system always spits out the message “going down on signal 18”,
which according to “kill -l” means that a child has exited.
I’ve tried including the terminfo files in /usr/lib/terminfo/q/ to see if it
is a problem with the terminal settings, but that didn’t seem to help.

Does anyone have any ideas or can someone please lend me a hand getting
started here, point me to examples, other references which may help? I’ve
looked all over the QNX on-line documentation and found no real info as to
the proper configuration, what is absolutely needed, etc.

Thanks in advance.

Regards,
Jason

2

Jason Wycoff <jason@socratec.de> wrote:

Hello everyone.

I’m trying to integrate telnetd into a embedded PC104-based system with
Neutrino and am having loads of trouble figuring out how to get telnetd to
work so that we can do some basic maintenance work on the embedded system.
I’ve already made the build files and got the ftpd server up and running
fine.
When I try to log into the system from my QNX development PC, I am allowed
to enter the username and password, but upon hitting enter after the
password, I immediately receive the notification “connection closed by
foreign host”
The embedded system always spits out the message “going down on signal 18”,
which according to “kill -l” means that a child has exited.
I’ve tried including the terminfo files in /usr/lib/terminfo/q/ to see if it
is a problem with the terminal settings, but that didn’t seem to help.

This might be a stupid question, but you put the files in the same
place on the target, right?

As well make sure your are running devc-pty.


regards,
Tom

3

Hi Tom,
thanks for your reply.

Yes, I’m running devc-pty (with the default 8 pseudo-tty devices), and I’ve
copied the terminfo files into the same path on the target. Strangely, when
I telnet from my windows box, the windows telnet session simply hangs when I
enter the password, on my QNX development PC I get the “connection closed”
message. I’m really stumped here and don’t know how to continue.

This is a typical situation, which I’ve encountered again and again. I’m no
unix guru and it seems that QNX is missing some sort of “solutions recipe
book”, which shows common solutions to recurring problems, especially those
dealing with system configuration. For a newbie like me this is very
frustrating, as I’m not event aware of all the available possibilities, and
end up discovering them by chance. Sorry, a bit off the topic there, as
much as I like what I see in the product QNX, this has been my eternal
complaint :slight_smile:

If you have any more ideas regarding telnetd, I’ll really appreciate them.

Regards,
Jason


This might be a stupid question, but you put the files in the same
place on the target, right?

As well make sure your are running devc-pty.


regards,
Tom

4

Jason Wycoff <jason@socratec.de> wrote:

Hi Tom,
thanks for your reply.

Yes, I’m running devc-pty (with the default 8 pseudo-tty devices), and I’ve
copied the terminfo files into the same path on the target. Strangely, when
I telnet from my windows box, the windows telnet session simply hangs when I
enter the password, on my QNX development PC I get the “connection closed”
message. I’m really stumped here and don’t know how to continue.

Hmm, I believe in a news group Sean B. gave a list of files.

A few simple thoughts, make sure all files are in their default
location, for example /etc/passwd, /etc/shadow, /usr/lib/terminfo/…

Delays before the Username prompt are often caused by telnetd doing a reverse
DNS lookup of the host, so having telnet clients in the /etc/hosts file
if not found in the default DNS server will speed things along.

If you do get a ‘hang’, go to the server machine and run pidin to see
what processes are blocked on what, is anything continuously running ready.

Check out nicinfo (QNX 6) or netinfo -l (QNX 4) to see if you are experiencing
any network issues. There’s got to be something on the Windows box for the same.

Does login work on each QNX machine?

Can you use voyager to browse on each QNX machine?

Personally I have always found telnet to be very stable on QNX.

This is a typical situation, which I’ve encountered again and again. I’m no
unix guru and it seems that QNX is missing some sort of “solutions recipe
book”, which shows common solutions to recurring problems, especially those
dealing with system configuration. For a newbie like me this is very
frustrating, as I’m not event aware of all the available possibilities, and
end up discovering them by chance. Sorry, a bit off the topic there, as
much as I like what I see in the product QNX, this has been my eternal
complaint > :slight_smile:

You can try using the knowledge base

http://www.qnx.com/support/sd_bok/

A bit harder to find now, the web site is under re-construction. Hopefully
qdn.qnx.com will come back to life.

regards,
Tom