Contents:
Part Four:
Note:
Part Four is the final section of the documentation
for "Setting up a Remote Port Utility". Selecting the Next
button (above) takes you to the Contents page.
Using Remote Ports on
SCO UNIX
The precompiled binary of svr_tty was compiled and tested on SCO Unix
3.4v4.2, and should run on all versions of SCO UNIX. Valid pseudo-tty
master device names are: ptsp0, ptsp1, ..., and the corresponding slave
device names are: /dev/ttyp0, /dev/ttyp1, ... The daemon may be
started from an entry in /etc/inittab, e.g.:
ts:2:respawn:/etc/svr_tty
-D/tmp/svr_tty.log
Alternatively, an /etc/rc2.d script could be used.
Using Remote Ports on
Solaris
The precompiled binaries of svr_tty were compiled and tested on Solaris
2.4 (Intel only) and Solaris 2.5.1 (SPARC). Valid pseudo-tty names
are: pts/0, pts/1, ... and the corresponding slave device names are:
/dev/pts/0, /dev/pts/1, ... The daemon is started from an entry
in /etc/inittab:
ts:23:respawn:/etc/svr_tty
-D/tmp/svr_tty.log
Alternatively, an /etc/rc2.d script could be used.
Using Remote Ports on SunOS
The precompiled binary of svr_tty was compiled and tested on SunOS
4.1.4. Valid pseudo-tty master device names are: pts[pqrs][0-9a-f]
and the corresponding slave device names are: /dev/tty[pqrs][0-9a-f].
The daemon may be started by placing a command to invoke it in the file
/etc/rc.local:
/etc/svr_tty -D/tmp/svr_tty.log
Using Remote Ports on
UnixWare
The precompiled binaries of svr_tty were compiled and tested on UnixWare
2.1. Valid psuedo_tty names are: pts/0, pts1, ... and the corresponding
slave device names are: /dev/pts0, /dev/pts1, ...
The daemon may be started from an entry in /etc/inittab:
ts:23:respawn:/etc/svr_tty
-D /tmp/svr_tty.log
Alternatively, an /etc/rc2.d script could be used.
Using Remote
Ports on Other Types of UNIX
The simplest way to implement the remote port facility on a new operating
system is to start with the compilation flags and configuration information
for a similar system, and modify as necessary.
The main differences between operating systems occurs in the psuedo_tty
implementation. There are two major flavours: Berkely (BSD)
and System V Release 4.
You will need to:
- Find appropriate compilation flags and libraries to build svr_tty
(use -DSVR4 or SVR4 psuedo_tty names, otherwise you will get conventions)
- Use the appropriate psuedo_tty naming conventins in the svr_tty
configuration file
- Find an appropriate place to invoke the svr_tty daemon on system
startup. svr_tty should not be invoked until after any TCP/IP
initialisation has been performed, and should be invoked with superuser
priveledges.
Go to
Top of Page
