56 lines
2.4 KiB
HTML
56 lines
2.4 KiB
HTML
<HTML>
|
|
<HEAD>
|
|
<TITLE>SICS Client Configuration</TITLE>
|
|
</HEAD>
|
|
<BODY>
|
|
<H1>SICS Client Configuration</H1>
|
|
<P>
|
|
Currently, SICS clients are written in Tcl/TK. This means that these programs
|
|
are just scripts wich can be edited. Such editing is necessary in order to let
|
|
the clients know how to connect to a server. All client configuration
|
|
information is kept in an array named INI which is at the very top of the file.
|
|
Configurable values in INI are:
|
|
<DL>
|
|
<DT> DefUser
|
|
<DD> The SICS user name for the initial logon to the server when connecting.
|
|
<DT>DefPasswd
|
|
<DD> The password of the default user for logon.
|
|
<DT>ServerPort
|
|
<DD> The port number where the server is listening.
|
|
<DT>InterruptPort
|
|
<DD> The interrupt port number of the server.
|
|
<DT>box
|
|
<DD> The computer on which the SICS server is running.
|
|
<DT>usPasswd
|
|
<DD>The password of the SICS user. This is used as password when setting
|
|
user rights from the menu.
|
|
<DT>muPasswd
|
|
<DD>The password of the SICS managers. This is used as password when setting
|
|
user rights from the menu.
|
|
<DT>logpath
|
|
<DD>Only for the command line client. On request of the SICS users each
|
|
command line client logs all I/O into a logfile. This logfile resides on the
|
|
computer running the SICS server. This allows SICS managers to check what
|
|
user have done to the machine. The logpath element defines the path to the
|
|
directory where the automatically
|
|
created log files are kept on the computer running the SICS server.
|
|
</DL>
|
|
The rest of the parameters and the file is programmers only. Reasonable values
|
|
for those parameters can be found in the server configuration file. And of course,
|
|
you need to know where the server is running.
|
|
</P>
|
|
<p>
|
|
At the very top of the client script there is the full path name of the Tcl/TK
|
|
interpreter to run in. This must be a wish for the command line client and a
|
|
blt_wish for the status display client. This may need to be changed if a client
|
|
comes up with: command not found. Valid copies of these executables can be
|
|
found in /data/lnslib/bin. Tcl/TK needs own libraries of scripts as well. The
|
|
places where these libraries sit is defined through the environment variables
|
|
TCL_LIBRARY and TK_LIBRARY. Suitable libraries are under /data/lnslib. For
|
|
details inspect /data/lnlib/bin/lns.login. When moving a client to a machine
|
|
where the clients need to run stand alone this stuff needs to be copied and
|
|
TCL_LIBRARY and TK_LIBRARY properly defined in the .login file.
|
|
</p>
|
|
</BODY>
|
|
</HTML>
|