Auto-Start Scripts options
These configuration items are available on the Auto-Start Scripts GUI:
Field/Option | Description |
---|---|
These projects are controlled by auto-start scripts. When all projects are selected, they are always controlled by the auto-start scripts. It is unnecessary to update auto-start scripts for new projects. |
|
By default, all site processes are started by auto-scripts. Sites added to this list are excluded from auto-start. |
|
Sites repository file system |
When deploying CIS to the production environment, some sites that are created on replicated or shared file systems are linked to HCIROOT. When you link auto-start sites outside HCIROOT, you must set Sites repository file system. The auto-start scripts ensure that the link exists when the scripts start. |
This option applies in Windows systems. The existing NT service starts the host server. Setting this variable instructs the auto-start scripts to restart the host server. |
|
In most cases, auto-start scripts create multiple processes to start a configured site, one process for one site. This causes a failover. Having many sites start up in parallel exhausts the system resources and causes unexpected errors. In these instances, select . When this is selected, sites are started one-by-one. This saves system resources, but runs slower.The single process mode saves logs on Windows at HCIROOT/server/fake_stdout.txt and fake_stderr.txt. On Linux, a site’s startup log is created in sequence at /var/log/message. |
|
Running the hcidbdefrag command is helpful when you have a large number of messages in recovery . However, you must exercise caution. For example, if you have 200K messages, then the process takes many minutes, or hours, to complete. This option allows you to take control of the action, to avoid an unnecessarily long process time. |