---
name: "termtest"
section: "1"
platform: "linux"
package: "term"
version: "2.3.5"
release: "Debian 1.3 (Bo)"
platforms: ["linux"]
url: "https://new.carta.tech/termtest"
---

# termtest(1)

debugging tool for term

## NAME

termtest - debugging tool for  *term*

## SYNOPSIS

**termtest**  \[-1 \<program\>\] \[-2 \<program\>\] \[-local \<options\>\] \[--remote \<options\>\] \[\<options\>\]

## DESCRIPTION

You should perform two sets of tests before you ever try to run *term* itself. The *termtest* program lets you  exercise  *term* and its clients locally by starting two *term* daemons on the same system. *Termtest* when run, establishes two connected instances of  *term* on the local system so you may see if they and the clients work.   To avoid problems with other programs also called 'termtest' you should  run *termtest* from the source directory of  *term* by typing

   setenv TERMMODE 0

   ./termtest  -n  on

*Termtest* opens the files 'local.log' and 'remote.log' in the local directory to record the stderr output of the two term daemons. Options on the command line of **termtest** are passed on to both of them. If you need to debug you can use  **-d 64** or even **-d 2112.** Familiarity with the sources is essential if you use debugging. The termrc file is used to set the parameters of both daemons. You can specify a different term daemon (e.g. an old one that is already installed on your system) as the 'remote' by giving the option  **-2 program** as the first option for test. Similarly, you can use a different 'local' term daemon with the  **-1** option.

Once  *termtest* is running you should be able to use the clients from any shell:

   trsh

give you a 'remote' shell.  You may need to type 'reset ^J' to reset the tty of the new shell (that's Cntl-J).

   trsh -s who

will run the who command 'remotely' to list the current users.

   tupload -fvv \<filename\> ... /tmp

will copy the listed files into the /tmp directory and provide CPS statistics.

   tredir 4000 23

will map port 4000 to 23 and put itself in the background.  Then, typing

   telnet 0 4000

should give you a login prompt that works. If you're running X, you should be able to use  *txconn* to establish a new display (screen) that maps to the existing screen.

Be sure to run  *./termtest* on both the local and remote systems, particularly if the systems use different architectures.

## BUGS

## SEE ALSO

[*term*(1)](/term/1.md), [*termrc*(1)](/termrc/1.md), [*term\_setup*(1)](/term_setup/1.md), [*term\_clients*(1)](/term_clients/1.md), [*termtest*(1)](/termtest/1.md), [*linecheck*(1)](/linecheck/1.md).

## AUTHOR

Michael O'Reilly, michael@iinet.com.au, original author\
 Bill C. Riemers, bcr@physics.purdue.edu, current developer