Overview

Service Manager is a CCSP component which helps us to monitor the systemd process running on the device. There are two primary states defined for each systemd process "Running" and "Stopped". Using this component we can get to know all the system process currently running or stopped. Also we have the provision of switching the states of the processes on the device. This component uses a TR-181 object for the user to access the list of all the running processes and alter their state. 

Object

Service Manager component uses the following object

Device.X_RDKCENTRAL_COM_ServiceAgent.

Parameters

The parameters defined as part of above object are

Device.X_RDKCENTRAL_COM_ServiceAgent.Services.{i}.Name
Device.X_RDKCENTRAL_COM_ServiceAgent.Services.{i}.GoalState

We can configure the state of a process by setting the parameter "Device.X_RDKCENTRAL_COM_ServiceAgent.Services.{i}.GoalState". 

For Example to Start a systemd process lets say with index 1,

    $ dmcli eRT setv Device.X_RDKCENTRAL_COM_ServiceAgent.Services.1.GoalState string Running

Similarly to stop a systemd process use the following

    $ dmcli eRT setv Device.X_RDKCENTRAL_COM_ServiceAgent.Services.1.GoalState string Stopped
  • No labels

1 Comment

  1. Z-Tony He

    Hi,

    I did not find below object in the RPI4 2022q1 image. Anything wrong or has been changed since this document was updated on 2017?  Thanks!

    Device.X_RDKCENTRAL_COM_ServiceAgent.

    root@RaspberryPi-Gateway:~# dmcli eRT getv Device.X_RDKCENTRAL_COM_ServiceAgent.
    CR component name is: eRT.com.cisco.spvtg.ccsp.CR
    subsystem_prefix eRT.
    Can't find destination component.


DISCLAIMER: Please note that the use of the RDK Wiki is subject to its Privacy Policy & Terms of Use. In addition, this Wiki may be accessed by all RDK licensees and their contractors.