	These programs implement a mostly-transparent queueing and
remote-execution system for programs that do not require tty-level
access to the user.  That is, standard input and output can be
copied as with rsh, but ioctls and the like will fail.  The entire
package is extremely dependent on 4.[23] networking operations and
may have some remaining localisms; however, it has been used without
much trouble on recent Ultrix and SunOS machines.  There is at least
one assumption that may require attention:  when using a remote file
system, paths of the form /r/hostname/ are assumed to reach the root
of the remote host.  Worse, some assumptions that the same path name
is valid from different hosts have probably crept in.  Finally,
NFS became popular sometime in the early evolution of the queuer so
the modes of operation that do not require a remote file system
were not fully developed.  These restrictions aside, we have found
this package quite useful.
	In operation, a program to be queued is made non-executable
by the general public and a link is established from the queue program
to the name of the program in another directory on the user's path.
Alternately, the original program can be renamed and the link
established in the same directory as the original program.  A configuration
file is created in /usr/lib/queued with the same name as the queued
program.  Access to the original program is controlled by briefly
enabling world execution using the semantics of vfork() to minimize
the window; this has proved adequate in our environment.
	A list of potential execution hosts is specified in the
configuration file and these are tried in order of least load
(as determined by examining the rwho spool files) with the local
host being used as a last resort (unless specifically disabled).
This rather autonomous behavior can be can be made more deterministic
through the use of the qmaster program.
