40 lines
1.6 KiB
HTML
40 lines
1.6 KiB
HTML
<html>
|
|
<head>
|
|
<title> Overview of SICS Initialization </title>
|
|
</head>
|
|
<body>
|
|
<h2>Overview of SICS Initialization</h2>
|
|
<p>
|
|
The command to start the SICServer is: <b> SICServer inifile </b>. So, what
|
|
happens at the initialization of the SICS server? First, internally, a set
|
|
of standard SICS commands is initialized, than a set of special
|
|
initialization commands. These are special commands which help to configure
|
|
the SICS server to match the actual hardware present on the hall floor and
|
|
to define the commands available later on. Following this, the SICS server
|
|
will read the initialization file specified on the command line or servo.tcl
|
|
as a default. Using the data supplied in this file, the server will be
|
|
configured. At this stage all special initialization commands, all
|
|
Tcl-mechanisms and all SICS commands already initialized are available.
|
|
After this is done, the server will delete the initialisation commands from
|
|
its internal command list (No need to carry them around all the time). Now a
|
|
status backup file will be read. This file contains normal SICS statements
|
|
which initialise parameter values to the values they had before the last
|
|
shutdown of the server. Such a file is automatically written whenever a
|
|
normal shutdown of the server happens.
|
|
</p>
|
|
<p>
|
|
The SICS server configuration file is essentially a SICS macro language
|
|
file. This implies that all general SICS commands and Tcl mechanisms are
|
|
available. Additionally the configuration file (and only the configuration
|
|
file) may use special commands for the installation of:
|
|
<ul>
|
|
<li>SICS server options.
|
|
<LI>SICS variables.
|
|
<LI>Special commands.
|
|
<LI>Hardware
|
|
</ul>
|
|
</p>
|
|
|
|
</body>
|
|
</html>
|