Controlling services

Manage or control system services.

Viewing a consumer's system service
You can view the services that are associated with a particular consumer. You can also view services for all consumers.
Determining the host address where a system service runs
Registering a new service
Register a service if you need to add a new service or if you unregistered a service that you need again. If the service is set up to be manually started, you may need to enable the registered service later.
Unregistering a service
Updating a service
You can update a service by modifying parameters in the service profile.
Starting a service
Stopping a service
Disabling root user execution for EGO services
As a security best practice, only PEM should be run as root; any EGO services should be executed by a non-root user (such as by a cluster administrator user). This level of security avoids someone running malicious code as root user. You can prevent PEM from starting EGO services as the root user on the host by first setting EGO_DISABLE_ROOT_REX=Y in the ego.conf configuration file. You can then change your host settings to no longer allow a root user to execute services (you can switch to non-root user, or disable the service from automatically starting), and also remove any work files that were created by the root user, if they exist.
Scaling a service
Scale a service when you want to increase or decrease the number of service instances to adjust load during peak and low periods.
Terminating and releasing service instances
To manage workload more efficiently when lending resources, you may want to terminate and release service instances of an EGO service, especially those that are idle.
Service maintenance
When preparing for a temporary maintenance shutdown, you might want to freeze a service without releasing the resource.
Shutting down custom system services gracefully
If you are running a custom system service as an EGO service, you can specify a script to clean up and shut down service instances. If you do not have a shutdown script, you can simply enable service instances to be shut down. In both cases, you can configure a timeout during which the system waits for the target instance to exit. The system ends the target instance if it is still running after the timeout expires.

Parent topic: System services