Many commercially available transport protocols provide
remote execution capabilities that are tied to the protocols.
In UnixWare 7, the
command, for example, allows remote users to log into a host on
a TCP/IP network.
REXEC is a remote execution facility that
is independent of transport protocol.
It allows a user
to execute a process on a remote host, independent
of the transport provider.
To the user, remote execution of a process through
REXEC is transparent.
Once the user executes a process on a remote
machine, the user interfaces with the process as if it were running
However, all files referenced by a remote command are
relative to the server.
For example, if a user executes the
command remotely, a list of users
logged in to the remote machine is displayed, not a list of
users on the local machine.
For the system administrator, REXEC makes it possible to
administer a set of machines remotely from a single location,
without the overhead of logging in to the remote machines.
REXEC gives administrators the ability to:
REXEC is service-based.
A server defines services that a client
can execute remotely.
By default, when REXEC is first installed,
a server has the following standard services defined:
monitor the system activity of several machines from
a single machine
stop and start network applications, such as the Network File System (NFS)
tune the performance of a set of machines by specifying
that certain processes are to execute on a less active system
General instructions for invoking an REXEC service, as well as specific
instructions for using the standard services,
appear on the
A service that allows a user on a client to execute a command or
shell script on the server.
A service that allows a user on a client to log in to the server.
A service that allows a client user to list the services
available on a server for remote execution.
© 2004 The SCO Group, Inc. All rights reserved.
UnixWare 7 Release 7.1.4 - 22 April 2004