topic Re: Terminal gets stuck in one line in Operating System - HP-UX

Terminal gets stuck in one line

Stefan Schulz — Thu, 30 Aug 2001 08:51:49 GMT

Hi,

i do have a terminal problem where i just can't find the solution.

If i do a rlogin -l root my terminal gets stuck in one line. Although everything works, all comandsoutput and input is limited to one line. If i use a command like ls, everything is printed on this one line and the comand prompt returns also on this line.

Interesting : If i do a rlogin and then a su - everything is fine.

Til now i thought doing a rlogin -l root and doing an rlogin followed by a su - is exactly the same.

At the moment i don't know what to look for. What setting can cause this behavior? Why is there a difference in those two ways becomming root on the server? Exactly where is the difference?

The Client and the server are both running HP-UX 10.20. The user has teh same (mounted) homedirectory on the server and the client.

Any ideas??

Stefan

Re: Terminal gets stuck in one line

Victor BERRIDGE — Thu, 30 Aug 2001 08:56:52 GMT

Hi,
Have you checked how is set your terminal?
Have you tried: stty sane or TERM= with same result?

Regards
Victor

Re: Terminal gets stuck in one line

Stefan Farrelly — Thu, 30 Aug 2001 09:25:08 GMT

I find this problem is caused by using unusual sized windows. ie. not 80x24. If you spawn off a dtterm or hpterm at 80x24 and try it again it should get around the problem.

From a dtterm you can go to the menu bar at the top of the window and do a soft reset which will fix the lockup on one line.

For a more permanent solution you need to fix your .profile, there are some terminal test commands in there which cause the lockup on non regular sized windows. Try removing the .profile and that should work. Then you can create a new .profile and only add in what you need.

Re: Terminal gets stuck in one line

Magdi KAMAL — Thu, 30 Aug 2001 09:43:31 GMT

Hi Stefan,

I agree with Stefan (king) about the window sizing parameters.

I get this problem by increasing the size of window.

Also setting the TERM variable :

export TERM=.

Magdi

Re: Terminal gets stuck in one line

Stefan Schulz — Thu, 30 Aug 2001 10:46:26 GMT

Thanks a lot for your help. As Stefan and Magdi said it's a problem with the resized dtterm. It had nothing to do with the TERM environment.

What i still don't understand is why there is a difference between rlogin -l root and rlogin folowed by a su -. But i think that this has something to do with the different profiles which are active during this rlogin.

Ok, i will have a close look again on my profiles to remove everything thats not necessary.

Thanks again for your help.

Regards Stefan

Re: Terminal gets stuck in one line

Alex Glennie — Thu, 30 Aug 2001 11:21:51 GMT

This also looks interesting :
DocId: KBRC00000078
Updated 6/8/01 9:11:00 AM
PROBLEM

The scrolling area is not the full size of the dtterm window if the size is larger than
80x24 and a telnet or su - is executed.

RESOLUTION

When an "su -" or "telnet" is performed, /etc/profile is executed and uses "tset" to
detect and set the TERM type.

When queried, dtterm reports its terminal type as "vt220" --which is correct-- but vt200
and vt220 expect the window to be 80x24 or 132x24 (these terminal emmulators are not
resizable). "tset" will do a reset on the terminal, which will then force the window to be
configured for 80x24.
dtterm is simply a resizable vt220 emmulator.

To correct the problem, do the following:

1.Login as root on the machine
2.cd /usr/share/lib/terminfo/v
3.mv vt200 vt200-old
4.rm vt220 vt220-nam
5.ln ../d/dtterm vt200
6.ln ../d/dtterm vt220
7.ln ../d/dtterm vt220-nam

This will hard link the vt200 and vt220 terminfo database files to the database for
dtterm.
Since dtterm is a resizable version of vt200/vt220, there should not be any adverse side
effects. From then on "tset" in a dtterm generating vt200 will not be a problem.

Re: Terminal gets stuck in one line

Wodisch — Thu, 30 Aug 2001 19:53:23 GMT

Hello Stefan,

the line you are stuck in is the last one (bottom line),
right?
Most often it is enough to just call "reset", which is
perhaps done in the "/etc/profile" or root's ".profile",
being the reason why you do not have the problem
there...

Just my ?0.02,
Wodisch