XON(1) X Version 11(Release 4) XON(1)
NAME
xon - start remote X clients with minimum overhead
SYNOPSIS
xon [-l userid] [-debug] host cmd [arg ...]
DESCRIPTION
xon sets up permissions and starts an X11 client on a remote machine with
minimal overhead. It is a frontend for the remote shell facility (remsh
or rsh). It minimizes the number of open ptys on the remote and local
machine, and thus improves performance. The usual rsh/remsh and xhost
access controls apply.
Xon runs xhost to permit opening an X session from the remote host. It
propagates the DISPLAY variable from the local environment to the remote
session. It closes the local standard input, output, and stderr streams
so that the session is not associated with an unnecessary pty.
If the base name in the remote command is "xterm", xon will insert the
xterm option -name xterm-host. This allows X11 resource files to specify
different xterm colors and features depending on the target host.
OPTIONS
-l userid
Attempt to login with the userid userid.
-debug Do not close the input and output files, and display executed sh
statements.
SEE ALSO
X(1), xhost(1), rsh(1) or remsh(1)
ENVIRONMENT
DISPLAY Copied to the remote session's environment. It must be set.
If DISPLAY is set to "unix:n.n" or ":n.n" then DISPLAY is
changed to "hostname:n.n".
HOSTNAME Used when appropriate to modify the DISPLAY variable before
passing it on to the remote host. If HOSTNAME is not set, the
uname command is run to supply the appropriate value.
SHELL Used to determine whether to redirect stderr with ">&" (for
tcsh, csh) or "2>&1" (for bash, sh, ksh). If SHELL is
unassigned, xon assumes csh is your default shell.
BUGS
Care must be taken with quoting shell arguments for the remote session,
since some layers of quoting are already present. For best results, use
' instead of ".
10/89 Page 1
XON(1) X Version 11(Release 4) XON(1)
If you use csh on one machine and some other shell on another machine,
xon may not properly redirect input and/or may abort. There may be no
way to fix this, except to write a program.
AUTHORS
Originally suggested by Chris Torek (chris@mimsy.umd.edu). Successive
implementations by Marion Hakanson (hakanson@cse.ogc.edu), Jim Dempsey
(jjd@bbn.com), Stephen Gildea (gildea@bbn.com), Dan Greening
(dgreen@cs.ucla.edu).
Page 2 10/89