SEO

Hello,
I have an Ultra 2 server, and I use it in standard text mode (no GUI).
The problem is that some times, but not always, after quitting the
Veritas Netbackup 'bpadm' menu interface, the terminal starts to behave
strangely.
When typing UNIX commands and looking at the standard output, the
text first runs to the bottom of the screen, which is normal, and then,
instead of shifting each line up one space (and losing the top line) to
display the new line, it shifts everything about 15 lines up and runs to
the bottom of the screen again, to shift 15 lines up again and so on.

I tried to change 'stty' parameters to see what happens, but nothing
happens. I'm even unable to change 'rows' and 'columns' parameters. stty
seems to accept the value I give to these parameters, but when I type 'stty -a'
afterwards, I see it's keeping the old values of 34 rows and 80 columns and
never accept my values.

Now, just rebooting the machine will return to normal, but I'd like to see
and understand what's happening and fix the problem, without having to
reboot, because some of our servers can't reboot at any time.

Thanks for any help.

Louis-Luc

leguerri@canr.hydro.qc.ca wrote:
> Hello,
> I have an Ultra 2 server, and I use it in standard text mode (no GUI).
> The problem is that some times, but not always, after quitting the
> Veritas Netbackup 'bpadm' menu interface, the terminal starts to behave
> strangely.
> When typing UNIX commands and looking at the standard output, the
> text first runs to the bottom of the screen, which is normal, and then,
> instead of shifting each line up one space (and losing the top line) to
> display the new line, it shifts everything about 15 lines up and runs to
> the bottom of the screen again, to shift 15 lines up again and so on.
>
> I tried to change 'stty' parameters to see what happens, but nothing
> happens. I'm even unable to change 'rows' and 'columns' parameters. stty
> seems to accept the value I give to these parameters, but when I type 'stty -a'
> afterwards, I see it's keeping the old values of 34 rows and 80 columns and
> never accept my values.
>
> Now, just rebooting the machine will return to normal, but I'd like to see
> and understand what's happening and fix the problem, without having to
> reboot, because some of our servers can't reboot at any time.
>
> Thanks for any help.
>
> Louis-Luc
>
>

This may be of no help whatsoever (in which case, apols), but when the
screen is misbehaving, try "tput reset" - you will need your $TERM
variable set correctly beforehand, though.

On Wed, 19 Nov 2003, Beardy wrote:

> This may be of no help whatsoever (in which case, apols), but when the
> screen is misbehaving, try "tput reset" - you will need your $TERM
> variable set correctly beforehand, though.

There's also 'stty sane' which resets the terminal if you accidentally
screw it up by viewing a binary file. Not sure if this can be used to
sort out the OP's problem.

--
Chris

Chris Lawrence wrote:
> On Wed, 19 Nov 2003, Beardy wrote:
>
>
>>This may be of no help whatsoever (in which case, apols), but when the
>>screen is misbehaving, try "tput reset" - you will need your $TERM
>>variable set correctly beforehand, though.
>
>
> There's also 'stty sane' which resets the terminal if you accidentally
> screw it up by viewing a binary file. Not sure if this can be used to
> sort out the OP's problem.
>

True enough, but I believe that stty is on a higher level (standard
example is obviously setting the interpretation of del), whereas tput
sends terminal configuration ioctls amongst other things...

On Wed, 19 Nov 2003, Beardy wrote:

> True enough, but I believe that stty is on a higher level (standard
> example is obviously setting the interpretation of del), whereas tput
> sends terminal configuration ioctls amongst other things...

Useful info, cheers.

--
Chris

Chris Lawrence <news03@holosys.co.uk.invalid> writes:
>On Wed, 19 Nov 2003, Beardy wrote:
>
>> This may be of no help whatsoever (in which case, apols), but when the
>> screen is misbehaving, try "tput reset" - you will need your $TERM
>> variable set correctly beforehand, though.
>
>There's also 'stty sane' which resets the terminal if you accidentally
>screw it up by viewing a binary file. Not sure if this can be used to
>sort out the OP's problem.
>

Do NOT use "stty sane" on a Solaris serial port unless you know
exactly what you are doing. It changes the settings to 7 bits
and even parity, which are not the correct settings on Solaris
machines except in very rare cases. Even on a frame buffer
(video card) in text mode, the improper parity setting can cause
trouble for displaying parts of the ISO 8859-1 character set.

-Greg
--
Do NOT reply via e-mail.
Reply in the newsgroup.

>
> This may be of no help whatsoever (in which case, apols), but when the
> screen is misbehaving, try "tput reset" - you will need your $TERM
> variable set correctly beforehand, though.
>
It solves the problem! Thanks for your advise.

Louis-Luc

leguerri@canr.hydro.qc.ca wrote:
>>This may be of no help whatsoever (in which case, apols), but when the
>>screen is misbehaving, try "tput reset" - you will need your $TERM
>>variable set correctly beforehand, though.
>>
>
> It solves the problem! Thanks for your advise.
>
> Louis-Luc
>

Cool. Always glad to help... ;-)