EGO service controller.
The service controller is the first service that runs on top of the EGO kernel. It functions as a bootstrap mechanism for starting the other services in the cluster. It also monitors and recovers the other services. It is somewhat analogous to init on UNIX systems or Service Control Manager on Windows systems. After the kernel boots, it reads a configuration file to retrieve the list of services to be started.
The service controller acts as a client to the EGO kernel, requesting resource allocations for running services and instantiating activities to host those services. It ensures that all the services are running by detecting failures and restarting service instances based on the parameter settings in the Control Policy portion of the service profile.
egosc is started automatically by vemkd and exits when vemkd exits. Under normal circumstances, you do not need to start it manually.
Starts the daemon, reading from the EGO configuration file ego.conf in the specified directory, rather than from the directory set via the EGO_CONFDIR environment variable.
Starts the daemon to validate its configuration files in the specified directory and then exits.
egosc reads the configuration file ego.conf to retrieve the location of the service controller configuration information, specified by the EGO_ESRVDIR parameter.
egosc looks in the directory EGO_ESRVDIR/esc/conf/services to locate the services that it is to manage. Each service has a corresponding file in the services directory.