|
|
Can't top when login via ssh
|
|
|
|
Grizzled Veteran
Join Date: May 1999
Location: Seattle
Status:
Offline
|
|
I've been logging in to the other computers on my little local empire here using ssh but I get an error message when I try to run top on those machines:
Error opening terminal: network.
Does anyone know how to fix that?
thanks,
bd
|
1.25GHz PowerBook
i vostri seni sono spettacolari
|
|
|
|
|
|
|
|
Mac Elite
Join Date: Dec 2001
Location: Atlanta, GA, USA
Status:
Offline
|
|
Could be your terminal emulation. On the remote machone do "echo $TERM" and see what you get. If it's not a standard emulation (xterm, vt100, vt220) then you may have found the problem. If that's the case, then set TERM to a valid value.
|
Mac Pro 2x 2.66 GHz Dual core, Apple TV 160GB, two Windows XP PCs
|
|
|
|
|
|
|
|
Grizzled Veteran
Join Date: May 1999
Location: Seattle
Status:
Offline
|
|
I get back "network". How do I change the terminal type? Why should I have to do this on a newly installed sytem?
|
1.25GHz PowerBook
i vostri seni sono spettacolari
|
|
|
|
|
|
|
|
Mac Enthusiast
Join Date: Nov 2001
Location: Adelaide, South Australia
Status:
Offline
|
|
Originally posted by Boondoggle:
I get back "network". How do I change the terminal type? Why should I have to do this on a newly installed sytem?
If you're using tcsh as your shell on the "foreign" system just add the following line to your .cshrc file on the remote machine. (Create it if necessary. Also note that if there's a file called ".tcshrc" present it'll be executed in preference to any .cshrc file, so add the line there instead):
setenv TERM vt100
You'll then need to either log in again or issue the command "source ~/.cshrc" so that the new TERM setting is invoked. Should you not be using tcsh on the remote machine --check by entering the command
"echo $SHELL", the prescription is slightly different. But try
export TERM=vt100
and see if that works. With any luck it'll get you started. As to why it's necessary, it's probably that the remote account doesn't provide a default TERM type, or that the suggested type isn't recognised, so you're getting "network" as a locally-specified type for a *network* connection. Uh, I think I'll quit while I'm behind!
Cheers,
Paul
|
|
|
|
|
|
|
|
|
Grizzled Veteran
Join Date: May 1999
Location: Seattle
Status:
Offline
|
|
Thanks Paul, I'll give that a try!
|
1.25GHz PowerBook
i vostri seni sono spettacolari
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Forum Rules
|
|
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
|
HTML code is Off
|
|
|
|
|
|
|
|
|
|
|
|