DCON(1) DCON(1) NAME dcon, ndcon, rx, rogin, rsh - remote login and execution SYNOPSIS dcon [ option ] ... machine ndcon machine rx machine [ command-list ] /usr/bin/m/machine [ command-list ] /usr/inet/bin/rogin machine [ -l username ] /usr/inet/bin/rsh machine [ -l username ] [ command-list ] DESCRIPTION Dcon logs in to the computer whose Datakit address is machine. It is much like cu(1), but the only local escapes are hang up `~.' and a shell escape `~!'. Dcon normally tries to log in automatically, using the login id of the invoking user. To login explicitly, or to connect to machines that disallow such access, use option -l. Other options are: -v Verbose. Give play-by-play while logging in. -s Script. The machine argument names a file that guides login. The first line of the file is the machine name. Later lines are paired: a prompt word expected from the remote machine (including nonblank punctuation), with an input line to send upon receiving that prompt. All other words received while looking for prompts are ignored. Ndcon logs in to a remote computer similarly to dcon, but with a direct stream(4)-to-stream connection. In particular mux(9) layers may be downloaded across it. The only local escape is the quit signal (control-\). Legitimate answers to the subsequent prompt `dcon>>' are `i' [sic] to send the quit signal to the remote machine, `x' or `.' to exit ndcon, and `!command-list' to execute commands locally. Rx invokes a shell on the designated machine and passes the command-list to that shell. The standard input and output of the remote process are the standard input and output of rx. The standard error file from the remote process is the same as the standard output. The current directory, permis- sions and shell variables of the remote shell are what the DCON(1) DCON(1) user would get by logging in directly. Unquoted shell metacharacters are interpreted locally; quoted ones are interpreted on the remote machine. Rx with no command-list is equivalent to `dcon machine'. Directory /usr/bin/m contains machine names as commands: `/usr/bin/m/machine' with no argument gets an ndcon connec- tion; with arguments it does rx. If the directory is in the sh(1) search path, the names become commands for navigating the local cluster. Rogin and rsh are to ARPA internet as dcon and rx are to Datakit. A file `.rhosts' in the login directory for username on a receiving machine lists machine/user pairs that may log in as username without a password check. Pairs appear one per line separated by blanks. EXAMPLES rx overthere cat file1 > file2 copies remote file1 to local file2; for other ways to do the job, see push(1) and nfs(5) rx overthere cat file1 ">" file2 copies remote file1 to remote file2 FILES /usr/inet/lib/* /usr/inet/lib/hosts.equiv list of machines with identical users $HOME/.rhosts BUGS Dcon's function properly belongs in cu(1). Response `q' to ndcon's quit-signal prompt causes a local exit, not a remote quit signal. Scripts for the -s option typically contain passwords in the clear. This will compromise the security of the remote machine unless the login reaches a restricted environment. Scripts are not the same as those for uucp(1). The machine arguments of these commands are Datakit addresses, while the names in /usr/bin/m are shorthand - usually the last component of an address. Thus on the machine `astro/grigg', the machine `bistro/polya' will be called `bistro/polya' in dcon, ndcon and rx, but will be simply `polya' in the navigation command.