Okay, since my previous question was so easy…
Maybe this really isn’t an embedded question, but I don’t know.
When connected to the board via a serial link and qtalk, everything
works fine (now that the term problem is fixed). However, when I connect
via telnet, I get some odd symptoms. In all cases here, I am logged in
via both methods simultaneously, with identical logins and environments.
Using telnet, if I go to the /etc directory, for example, I can “ls” and
“ls -al” just fine. In the “/” directory, on the other hand, “ls” still
works, but “ls -al” gives:
ls -al
total 54885
And that is it. At that point, I have to type ^] quit. I can then
reconnect, and it continues to work ok.
Doing a bit more playing around, there appears to be some relationship
to size of the data. With a test file that contains 780 bytes, I can do
“more tmp.txt” via telnet and it will work a couple of times fine, and
then suddenly appear to hang. Often, if I wait awhile (a minute) it will
respond, though sometimes even then it has not returned. But even while
hung via telnet, via the serial/qtalk terminal I can execute the same
command and it works fine.
With a 714 byte file via telnet, what I see is that it always works. But
I do notice that sometimes it returns instantly, and sometimes there is
a pause of a couple of seconds (or even 5 or 6) before returning. As the
file gets larger, the problem gets worse. Again, via the serial port,
there is never a pause; it always works, even with large files.
So does all this trigger any thoughts on what might be happening?
I am running the ttcpip stack with QNX 6.2.1 on a Technologic Systems
TS5400 board.