Languages and Scripting

tcsh: No entry for terminal type "xterm"

 
JoseLuis2
Occasional Contributor

tcsh: No entry for terminal type "xterm"

Hi,

In 1), ksh is the login shell. Is that the cause that "tcsh" complains about the terminal?

1)

 

tehpu067::/var/opt/aat/a/hp> uname -a
HP-UX tehpu067 B.11.00 U 9000/800 144454651 unlimited-user license
tehpu067::/var/opt/aat/a/hp> ps
   PID TTY       TIME COMMAND
  3186 pts/2     0:00 ps
  1886 pts/2     0:00 ksh
tehpu067::/var/opt/aat/a/hp> cat .cshrc
#
# Default user .cshrc file (/usr/bin/csh initialization).
#
# @(#)B11.23_LR
# Usage:  Copy this file to a user's home directory and edit it to
# customize it to taste.  It is run by csh each time it starts up.

# Set up default command search path:
#
# (For security, this default is a minimal set.)

        set path=( $path )

# Set up C shell environment:

        if ( $?prompt ) then            # shell is interactive.
            set history=20              # previous commands to remember.
            set savehist=20             # number to save across sessions.
            set system=`hostname`       # name of this system.
            set prompt = "$system \!: " # command prompt.

            # Sample alias:

            alias       h       history

echo $TERM

            # More sample aliases, commented out by default:

            # alias     d       dirs
            # alias     pd      pushd
            # alias     pd2     pushd +2
            # alias     po      popd
            # alias     m       more
        endif
tehpu067::/var/opt/aat/a/hp> 
tehpu067::/var/opt/aat/a/hp> tcsh
xterm
tcsh: No entry for terminal type "xterm"
tcsh: using dumb terminal settings.

 

 

2)

 

tehpu091!hpemsm1:~ [23]> grep '^hpemsm1:' /etc/passwd
hpemsm1:*:109:20:para implantar FAST ;Responsable Soporte al Desarrollo:/home/hpemsm1:/usr/bin/tcsh
tehpu091!hpemsm1:~ [25]> uname -a
tehpu091!hpemsm1:~ [25]> 
HP-UX tehpu091 B.11.23 U 9000/800 3817456798 unlimited-user license
tehpu091!hpemsm1:~ [26]> ps
   PID TTY       TIME COMMAND
 13356 pts/2     0:00 ps
 12642 pts/2     0:00 tcsh
tehpu091!hpemsm1:~ [27]> cat .csh
.cshrc       .cshrc.back
tehpu091!hpemsm1:~ [27]> cat .cshrc
#
# Default user .cshrc file (/usr/bin/csh initialization).
#
# @(#)B11.23_LR
# Usage:  Copy this file to a user's home directory and edit it to
# customize it to taste.  It is run by csh each time it starts up.

# Set up default command search path:
#
# (For security, this default is a minimal set.)

        set path=( $path )

# Set up C shell environment:

        if ( $?prompt ) then            # shell is interactive.
            set history=20              # previous commands to remember.
            set savehist=20             # number to save across sessions.
            set system=`hostname`       # name of this system.
            set prompt = "$system \!: " # command prompt.

            # Sample alias:

            alias       h       history

echo $TERM

            # More sample aliases, commented out by default:

            # alias     d       dirs
            # alias     pd      pushd
            # alias     pd2     pushd +2
            # alias     po      popd
            # alias     m       more
        endif
tehpu091!hpemsm1:~ [28]>
tehpu091!hpemsm1:~ [28]> tcsh
xterm
tehpu091!hpemsm1:~ [22]> exec ksh
$ ps
   PID TTY       TIME COMMAND
 26873 pts/2     0:00 ksh
 27098 pts/2     0:00 ps
$ tcsh
xterm
tehpu091 22:

 

 

Thanks in advance.

Regards, Jose Luis.

1 REPLY 1
KishJ
HPE Pro

Re: tcsh: No entry for terminal type "xterm"

Hello,

The terminal information is available at the following locations:

/usr/share/lib/terminfo
/usr/local/share/terminfo

I hope these directories are available and are exported via PATH variable

# echo $PATH

Next, you seem to be using 11.23 .cshrc on 11.00 and for "tcsh". First of all, I could not see any documentation that suggest tcsh uses this file. Assuming it does, does tcsh behave differently while using a file of 11.23? I am not sure.

Since, it is an ascii text file I think compatibility may not be an issue but I suggest to avoid, if at all possible any risks due to version difference. This means, if you have a backup 11.00 or any other server you may copy it over. 


I am a HPE Employee

Accept or Kudo