xon - start an X program on a remote computer


xon remote-host [-access] [-debug] [-name window-name]
	[-nols] [-screen screen-no] [-user user-name]
	[command ...]


The xon(1) utility runs the specified command (default xterm -ls) on the remote computer using rsh(1). The xon(1) utility passes the DISPLAY, XAUTHORITY and XUSERFILESEARCHPATH environment variables to the remote command.

When no command is specified, xon(1) runs xterm -ls. It additionally specifies the application name to be xterm-remote-host and the window title to be -fIremote-host.

The xon(1) utility can only work when the remote host will allow you to use rsh, by having an entry in the .rhosts file permitting access.


Note that the options follow the remote host name (as they do with rlogin(1)).

Run xhost locally to add the remote host to the host access list in the X server. This will not work unless xhost has permission to modify the access list.
Normally, xon(1) disconnects the remote process from stdin, stdout and stderr to eliminate the daemon processes that usually connect them across the network. Specifying the -debug option leaves them connected so that error messages from the remote execution are sent back to the originating host.
-name window-name
Set the application name and window title for the default command (xterm(1)).
Normally xon(1) passes the -ls option to the remote xterm(1); this option suspends that behavior.
-screen screen-no
Change the screen number of the DISPLAY variable passed to the remote command.
-user user-name
By default, xon(1) simply uses rsh to connect to the remote computer using the same user name as on the local computer. This option causes xon(1) to specify an alternative user name. This will not work unless you are authorized to access the remote account through rsh by placing an appropriate entry in the remote user's .rhosts file.


The xon(1) utility can get easily confused when the remote-host, user-name or various environment variable values contain white space.

The xon(1) utility has no way to send the appropriate X authorization information to the remote host.