make_tape_recovery

[Randy_9]

I've got 2 systems running 10.20, when I run
"make_tape_covery -i" on one it pops into the
character based utility, on the other I get:
*****************************************
Do you want to proceed in setting your TERM value and running
mnr_ui? (yes or no) [yes]

Input the correct value for your terminal or press "return" to set
the default TERM value = hp. TERM = (hp)
******************************************'
I am using EXCEED from a PC and the TERM type
is "dtterm", it works on the other one, here
no matter what I try (hpterm, vt100, dtterm)
it all fails and I had to just bomb out. Any
ideas?.

Thanks,

Randy

[Sanjay_6]

Hi Randy,

Before running the make_tape_recovery, export your TERM value and try,

export TERM=dtterm

Hope this helps.

Regds

[Martin Johnson]

After you are logged in, but before you use ignite, what does echo $TERM return.

You can try setting TERM before using ignite:

TERM=dtterm; export TERM

Also check that the same shell is being used on both systems:

grep username /etc/passwd



Marty

[Randy_9]

Sanjay and Martin,

The other system is using the same shell
(ksh as the root user on both). The TERM
value is "dtterm" on both? The program
error:

mnr_ui does not support this type of terminal. You must set TERM
to a value that is supported by mnr_ui and compatible with your
terminal.

"mnr_ui" says it doesn't support hp, hpterm,
dtterm, vt100. As I've tried them all and it
barks right back at me. Even though my TERM
already = dtterm, I re-exported it and it failed again?.

Thanks,

Randy

[Martin Johnson]

Have you check that you are running the same versions of ignite?

If you are not at the latest version (it sounds like you are not), you may want to upgrade?

Marty

[Helen French]

I think this is a bug with the program itself. The mnr_ui error normally comes when you invoke make_net_recovery and the Network system recovery GUI. Make sure that you have the latest ignite installed.

just a thought ..

[Randy_9]

PROBLEM RESOLVED:

The version of Ignite was the same as the neighboring system. I removed and re-installed
the Ignite s/w and that resolved the problem.
I just want to say thanks to everyone for
your time and help!

Have a great day and keep up the good work!

Randy

[Bill Hassell]

WARNING: You wrote:

"The other system is using the same shell
(ksh as the root user on both)."

BIG PROBLEMS AHEAD. The root shell on HP-UX must be /sbin/sh and never changed. /sbin/sh is the POSIX shell (NOT Bourne shell) and is actually a superset of ksh (which is also a POSIX shell). /sbin contains archived library executables, a fancy name for self-contained executables. On the other hand, /usr/bin executables require shared libraries (found in /usr/lib) but will not be available when running in single user mode.

This the 2 systems you mentioned will not run in single user mode as /usr/bin/ksh cannot find it's libraries.

Most sysadmins change HP-UX root shell to ksh (or bash) because they are familiar with other vendors who supply the Bourne shell as sh. The HP POSIX shell has all the features of ksh and more (try ulimit -a in ksh and then /sbin/sh).

Another reason is to switch to ksh is to get command stack recall working. It works fine but requires the env variable HISTFILE to be set at login (ksh uses it too but it is optional). Just add this to /etc/profile:

export HISTFILE=$HOME/.profile

And change root back to /sbin/sh. NOTE: you can always login as root and type: ksh