CON(1) CON(1)
NAME
con, rx - remote login and execution
SYNOPSIS
con [ -l ] machine
rx [ -n ] machine [ command-word ... ]
/usr/bin/m/machine [ command-word ... ]
DESCRIPTION
Con connects to the computer whose network address is
machine and logs in if possible. Standard input and output
go to the local machine. Option -l prevents automatic
login; a normal login dialog ensues.
The quit signal (control-\) is a local escape. It prompts
with the local machine name and >>. Legitimate responses to
the prompt are
i Send a quit [sic] signal to the remote machine.
q, x, or .
Exit.
b Send a break.
!command Execute command locally.
Rx executes one shell command on the remote machine as if
logged in there, but with local standard input and output.
Unquoted shell metacharacters in the command are interpreted
locally, quoted ones remotely. The assignment REXEC=1
appears in the remote environment. With no arguments, rx
just diagnoses availability. Option -n ignores sporadic
end-of-file indications on a sick network.
Network addresses for both con and rx have the form
network!host or simply host. Supported networks are `dk'
(Datakit) and `tcp' (TCP/IP, usually Ethernet).
Directory contains machine names as commands:
/usr/bin/m/machine with no argument runs an appropriate fla-
vor of con for the named machine. If given arguments,
/usr/bin/m/machine runs rx with those arguments. If is in
the sh(1) search path, the names become commands for navi-
gating the local cluster.
EXAMPLES
rx overthere cat file1 >file2
Copy remote file1 to local file2.
rx overthere cat file1 ">file2"
CON(1) CON(1)
Copy remote file1 to remote file2.
eqn paper | rx pipe troff -ms | rx arend lp
Parallel processing: do each stage of a pipeline on a
different machine.
FILES
authentication
servers
SEE ALSO
push(1), dcon(1), cu(1), dkmgr(8), svcmgr(8), tcpmgr(8),
ipc(3)
D. L. Presotto, `Interprocess Communication in the Eighth
Edition UNIX System', this manual, Volume 2
BUGS
The remote standard error and standard output are combined
and go inseparably to the local standard output.
Under rx, a program that should behave specially towards
terminals may not: sh(1) will not prompt, vi(1) will not
manage the screen, etc. Nrx (see dcon(1)) avoids this trou-
ble, but has others of its own.
Con and rx may not guess the right kind of connection. In
case of trouble, try the programs in dcon(1).
The names in are conventions, not actual network addresses.