Signature-based service manager with dependency checking
The present disclosure relates to systems and methods of implementing a service manager. In particular, the present disclosure relates to methods of monitoring a plurality of services, wherein each service is uniquely identifiable in a process table based on a fingerprint; receiving a request to add a new service to the plurality of services; determining whether service dependencies in a configuration of the plurality of services and the new service are compatible; and responsive to determining that the service dependencies in the configuration of the plurality of services and the new service are compatible, starting the new service. The method may further include receiving a request to call a user-defined function and determining whether the new service is functional based on executing the user-defined function.
1. A computer-implemented method comprising:
monitoring a plurality of services, wherein:
each service is a process managed by an operating system and running on a computer, wherein the process is uniquely identifiable in a process table of the operating system based on a signature;
the signature is based on a combination of at least two service attributes in an entry in the process table for the process, wherein at least one service attribute of the at least two service attributes comprises one or more of a file system location and a command line argument associated with the service;
the signature excludes a unique process identifier assigned to the process and included in the entry for the process in the process table; and
the signature is used to identify each of the plurality of services in the process table for monitoring the plurality of services;
receiving a request to add a new service to the plurality of services;
determining, using signatures to lookup processes in the process table, whether service dependencies of the plurality of services in the process table and the new service are compatible; and
responsive to determining that the service dependencies of the plurality of services in the process table and the new service are compatible:
starting the new service; and
determining a new signature for the new service based on a new entry in the process table for the new service.
2. The computer-implemented method of claim 1 , wherein:
at least one service attribute of the at least two service attributes comprises one or more of a process name, a process state, process control data, a priority, parent process information, a process group, user identification data, flags, and a name of a binary file associated with the service.
3. The computer-implemented method of claim 1 , wherein determining whether the service dependencies of the plurality of services in the process table and the new service are compatible comprises:
determining that the plurality of services in the process table are compatible with the new service in response to determining that a prerequisite service of the new service exists in the process table.
4. The computer-implemented method of claim 1 , wherein determining whether the service dependencies of the plurality of services in the process table and the new service are compatible comprises:
determining that the plurality of services in the process table are not compatible with the new service in response to determining that the new service and a prerequisite service of the new service create an infinite loop.
5. The computer-implemented method of claim 1 , wherein determining whether the service dependencies of the plurality of services in the process table and the new service are compatible comprises:
determining that the plurality of services in the process table are not compatible with the new service in response to determining that the new service requests a disabled service.
6. The computer-implemented method of claim 1 , wherein determining whether the service dependencies of the plurality of services in the process table and the new service are compatible comprises:
determining that the plurality of services in the process table are not compatible with the new service in response to determining that the new service requests to both start and stop a prerequisite service of the new service.
7. The computer-implemented method of claim 1 , wherein determining whether the service dependencies of the plurality of services in the process table and the new service are compatible comprises:
determining that the plurality of services in the process table are not compatible with the new service in response to determining that the new service requests to start itself.
8. The computer-implemented method of claim 1 , wherein determining whether the service dependencies of the plurality of services in the process table and the new service are compatible comprises:
determining that the plurality of services in the process table are not compatible with the new service in response to determining that the new service requests to stop itself.
9. The computer-implemented method of claim 1 , further comprising:
responsive to determining that the service dependencies of the plurality of services in the process table and the new service are compatible:
receiving a return code of the new service; and
determining that the new service started up successfully based on the return code.
10. The computer-implemented method of claim 1 , further comprising:
responsive to determining that the service dependencies of the plurality of services in the process table and the new service are compatible:
receiving a request to call a user-defined function; and
determining whether the new service is functional based on executing the user-defined function.
11. A system comprising:
one or more processors; and
a memory storing instructions that, when executed by the one or more processors, cause the one or more processors to:
monitor a plurality of services, wherein:
each service is a process managed by an operating system and running on a computer, wherein the process is uniquely identifiable in a process table of the operating system based on a signature;
the signature is based on a combination of at least two service attributes in an entry in the process table for the process, wherein at least one service attribute of the at least two service attributes comprises one or more of a file system location and a command line argument associated with the service;
the signature excludes a unique process identifier assigned to the process and included in the entry for the process in the process table; and
the signature is used to identify each of the plurality of services in the process table for monitoring the plurality of services;
receive a request to add a new service to the plurality of services;
determine, using signatures to lookup processes in the process table, whether service dependencies of the plurality of services in the process table and the new service are compatible; and
responsive to determining that the service dependencies of the plurality of services in the process table and the new service are compatible:
start the new service; and
determine a new signature for the new service based on a new entry in the process table for the new service.
12. The system of claim 11 , wherein:
at least one service attribute of the at least two service attributes comprises one or more of a process name, a process state, process control data, a priority, parent process information, a process group, user identification data, flags, and a name of a binary file associated with the service.
13. The system of claim 11 , wherein to determine whether the service dependencies of the plurality of services in the process table and the new service are compatible, the instructions cause the one or more processors to:
determine that the plurality of services in the process table are compatible with the new service in response to determining that a prerequisite service of the new service exists in the process table.
14. The system of claim 11 , wherein to determine whether the service dependencies of the plurality of services in the process table and the new service are compatible, the instructions cause the one or more processors to:
determine that the plurality of services in the process table are not compatible with the new service in response to determining that the new service and a prerequisite service of the new service create an infinite loop.
15. The system of claim 11 , wherein to determine whether the service dependencies of the plurality of services in the process table and the new service are compatible, the instructions cause the one or more processors to:
determine that the plurality of services in the process table are not compatible with the new service in response to determining that the new service requests a disabled service.
16. The system of claim 11 , wherein to determine whether the service dependencies of the plurality of services in the process table and the new service are compatible, the instructions cause the one or more processors to:
determine that the plurality of services in the process table are not compatible with the new service in response to determining that the new service requests to both start and stop a prerequisite service of the new service.
17. The system of claim 11 , wherein to determine whether the service dependencies of the plurality of services in the process table and the new service are compatible, the instructions cause the one or more processors to:
determine that the plurality of services in the process table are not compatible with the new service in response to determining that the new service requests to start itself.
18. The system of claim 11 , wherein to determine whether the service dependencies of the plurality of services in the process table and the new service are compatible, the instructions cause the one or more processors to:
determine that the plurality of services in the process table are not compatible with the new service in response to determining that the new service requests to stop itself.
19. The system of claim 11 , wherein the instructions further cause the one or more processors to:
responsive to determining that the service dependencies of the plurality of services in the process table and the new service are compatible:
receive a return code of the new service; and
determine that the new service started up successfully based on the return code.
20. The system of claim 11 , wherein the instructions further cause the one or more processors to:
responsive to determining that the service dependencies of the plurality of services in the process table and the new service are compatible:
receive a request to call a user-defined function; and
determine whether the new service is functional based on executing the user-defined function.
21. A system, comprising:
means for monitoring a plurality of services, wherein:
each service is a process managed by an operating system and running on a computer, wherein the process is uniquely identifiable in a process table of the operating system based on a signature;
the signature is based on a combination of at least two service attributes in an entry in the process table for the process, wherein at least one service attribute of the at least two service attributes comprises one or more of a file system location and a command line argument associated with the service;
the signature excludes a unique process identifier assigned to the process and included in the entry for the process in the process table; and
the signature is used to identify each of the plurality of services in the process table for monitoring the plurality of services;
means for receiving a request to add a new service to the plurality of services;
means for determining, using signatures to lookup processes in the process table, whether service dependencies in the plurality of services and the new service are compatible means for starting, the responsive to determining that the service dependencies of the plurality of services and the new service are comparible, the new service.
22. The computer-implemented method of claim 1 , wherein the signature for each service is determined by processing the combination of at least two service attributes by a process selected from concatenation and calculating a hash.
23. The system of claim 21 , wherein the signature for each service is determined by processing the combination of at least two service attributes by a process selected from concatenation and calculating a hash.