next up previous contents index
Next: Bibliography Up: The wrspiced Daemon: Remote Previous: SPICE Server Configuration   Contents   Index

Client Configuration

If the SPICE server is using a port number other than the default 3004, it is necessary to inform the clients of the actual port used. This can be done in two ways. One way is to modify the services database, as discussed above, setting the port for ``spice/tcp'' to the number used by the server. It might be wise to add this entry to the /etc/services files of the clients in any case, to let others know that the port is in use.

The second method is to specify the port number when specifying the SPICE host name to Xic and WRspice. The host name can have the following form:

hostname[:port]
i.e., the host name can be suffixed by a colon-delimited number which gives the port.

A WRspice server can receive jobs from Xic, and from WRspice (rspice command). Both programs have means by which the SPICE server can be specified from within the program. One means common to both programs is through use of the SPICE_HOST environment variable. The variable should be set to the host name of the SPICE server, as resolvable by the client, followed by the optional colon and port number. When set, Xic will by default use this server for SPICE jobs initiated with the Run button in the side menu, and WRspice will use this host in the rspice command. In a situation where the SPICE server provides the only SPICE available, the SPICE_HOST variable should be set in the user's shell startup script. In WRspice the rhost shell variable and the rhost command can also be used to specify the remote host, and these override any value set in the environment.

Note: In Xic, when WRspice connects, a message is printed in the terminal window similar to

Stream established to wrspice://chaucer, port 4573.
The ``port'' in this case is not the wrspiced port discussed above.


next up previous contents index
Next: Bibliography Up: The wrspiced Daemon: Remote Previous: SPICE Server Configuration   Contents   Index
Stephen R. Whiteley 2006-10-23