You can register one or more of database servers, CUBRID brokers, CUBRID Manager(s) or CUBRID HAs as CUBRID service in the configuration file (cubrid.conf). If you do not register any service, only master process is registered by default. It is convenient for you to view status of all related processes at a glance or start and stop the processes at once with the cubrid service utility once it is registered as CUBRID service. For details on CUBRID HA configuration, see Utilities of cubrid service.
The following example shows how to register database server and broker as service in the cubrid.conf file and enable databases (demodb and testdb) to start automatically at once when CUBRID server starts running.
# The list of processes to be started automatically by 'cubrid service start' command
# Any combinations are available with server, broker, manager and heartbeat.
# The list of database servers in all by 'cubrid service start' command.
# This property is effective only when the above 'service' property contains 'server' keyword.