3 rcpu, rimport, rexport, rconnect \- connection to CPU server
85 .I localcommand arg ...
90 on a cpu server with the local namespace exported to
93 The current directory, interrupt notes, standard file descriptors 0,1,2
96 are passed to the remote side. The command to run can be passed
100 otherwise an interactive shell is started. The user's profile
101 is run before the command with
105 to allow further customization of the environment (see
107 for more information).
108 The cpu server can be specified with
111 otherwise it defaults to the environment variable
117 mounts a remote directory
121 into the local namespace at
125 is omitted, it is set the same as
130 option is present, the service is also posted to
132 allowing it to be mounted in other namespaces.
137 exporting a local directory
141 and optionally executing
143 on the server side after posting the service to
149 is a helper program handling client side connection setup for
150 the commands listed above. The rcpu protocol starts by setting up a mutual
151 authenticated and encrypted TLS connection using
153 followed by the client sending an
156 file to the server which gets executed under the authenticated user
157 with file descriptors 0,1,2 cross connected to file descriptors 0,1
158 of the client side running
160 over the encrypted connection.
162 The common options are:
176 Restricts the set of exported files (see
184 Remote user id to authenticate as.
189 to select a key to authenticate to the remote side (see
193 Protect the connection against connection resets by establishing
197 .B /rc/bin/service/tcp17019