xon - start an X program on a remote machine
xon remote-host [-access] [-debug] [-name window-name] [-nols] [-screen screen-no] [-user user-name] [command...]
Note that the options follow the remote host name (as they do with
locally to add the remote host
to the host access list in the X server. This will not work unless xhost
is given permission to modify the access list.
disconnects the remote process
from stdin, stdout and stderr to eliminate the daemon processes which usually
connect them across the network. Specifying the
leaves them connected so that error messages from the remote execution are
sent back to the originating host.
This specifies a different application name and window title
for the default command (xterm).
Normally xon passes the
option to the
remote xterm; this option suspends that behaviour.
This changes the screen number of the
variable passed to the remote command.
to connect to the remote machine using the same
user name as on the local machine. This option cause xon to specify an alternative
user name. This will not work unless you have authorization to access the
remote account, by placing an appropriate entry in the remote users
The xon program runs the specified command (default xterm -ls) on the remote machine using rsh, remsh, or rcmd. xon passes the DISPLAY, XAUTHORITY and XUSERFILESEARCHPATH environment variables to the remote command.
When no command is specified, xon runs 'xterm -ls'. It additionally specifies the application name to be 'xterm-remote-host' and the window title to be 'remote-host'.
can only work when the remote host will allow
you to log in without a password, by having an entry in the
file permitting access.
xon can get easily confused when the remote-host, user-name or various environment variable values contain white space.
xon has no way to send the appropriate X authorization information to the remote host.