Auto-Start scripts
The Auto-start script UI is a tool for configuring auto-start scripts. This is controlled by application/hciserveradmin in advanced security mode. There is no access control in basic security mode. By default, the settings are stored in autostart/as.hci.profile.
If server/auto-start.profile is present, then it has higher priority than the first one.
If server/auto-start.profile is added after editing the auto-start scripts, then the host server must be restarted to make the read/write location point to the new location.
Auto-start features and options:
Feature | Description |
---|---|
Projects |
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. |
Excluded processes |
By default, all project processes are started by auto-scripts. Projects added to this list are excluded from auto-start. |
Projects repository file system |
When deploying CIS to the production environment, some projects that are created on replicated or shared file systems are linked to HCIROOT. When auto-start projects are linked outside HCIROOT, you must set the "Projects 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 project, one process for one project. This causes a failover. Having many projects start up in parallel exhausts the system resources and causes unexpected errors. In these instances, select HCIROOT/server/fake_stdout.txt and fake_stderr.txt. . When this is selected, projects are started one-by-one. This saves system resources, but runs slower. The single process mode saves logs on Windows atOn Linux, a project’s start-up log is created in sequence at /var/log/message. |
|
Running the hcidbdefrag command can be 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. |