Well the problem is resolved: I had the user reboot their PC and try a new
connection to the server. This worked fine.
Many thanks to Tom Blinn for a good education on termcaps. The questions
and answers are included in this summary:
Question:
I have a remote user who accesses this server (Alpha 8400, Tru64 4.0F PK4)
via T1 line by using Hummingbird Exceed. Theuser is all of a sudden getting
the error message listed below. I have never seen this and was wondering
just what it is telling the user. Any advise or pointers would be
appreciated.
%
Warning: incomplete termcap entry. Editing disabled.
% nohup /usr/bin/X11/xterm -display 166.76.188.133:0 -sb &
[1] 13167
%
Thanks,
Dennis Peacock
Answer:
Consider the possibility that you actually have an incomplete termcap entry.
Look at man 4 termcap; if you have a corrupted file, then things like the
xterm editing won't work right. That's what it's complaining about. You
might have a corrupted file and only see it for a few terminal types. I
have no idea what TERM setting the user is trying to use, but there are
things you can get wrong in the user environment that can lead to this
sort of error, as well.
Tom
Question:
Tom,
Thanks for the reply and info. The funny thing is that it is only ONE user
and not all of them......
I have about 30 users (a customer of ours) who accesses their servers from a
remote location here in the U.S. and they normally use Exceed for the
XWindows environment. I have some of them now using VNC with great success.
Would an incomplete termcap file effect a single user?
Thank You,
Dennis Peacock
Answer:
I think it could. You need to know the context in which it's
being accessed; there might be bad entries in the standard file
and this user has managed to set up his or her environment (via
shell initialization, for instance) to try to use a terminal
type for which the data is missing or incomplete. Happens. It
can be on a per-user basis precisely because different users
might be using different terminal types. People often wind up
putting terminal-specific logic in shell scripts because they
use only one terminal type, then try to use something that's
different and it breaks.
Tom
Thanks to all for your assistance,
Dennis Peacock
Acxiom Corporation
Received on Tue Jul 24 2001 - 19:52:06 NZST