Long-Term Supported Versions

    Innovation Versions

      sysMaster User Guide


      sysMaster is a collection of ultra-lightweight and highly reliable service management programs. It provides an innovative implementation of PID 1 to replace the conventional init process. Written in Rust, sysMaster is equipped with fault monitoring, second-level self-recovery, and quick startup capabilities, which help improve OS reliability and service availability.

      sysMaster manages processes, containers, and VMs centrally, and is ideal for server, cloud computing, and embedded scenarios.

      sysMaster divides the functions of traditional PID 1 into a 1+1+N architecture based on application scenarios.

      As shown in the figure, sysMaster consists of three components:
      • sysmaster-init, a new implementation of PID 1, is applicable to embedded systems with functions such as system initialization, zombie process recycling, and keep-alive monitoring.
      • sysmaster-core undertakes the core service management functions and incorporates the reliability framework to enable live updates and quick self-recovery in the event of crashes, ensuring 24/7 service availability.
      • sysmaster-exts offers a collection of components (such as devMaster for device management and busMaster for bus communication) that deliver key system functions. You can choose the components to use as required.

      Figure 1 sysMaster architecture

      Currently, sysMaster consists of the sysmaster and devmaster services, which manages services and devices, respectively. Their functions will be described in the following sections.

      Intended Audience

      This document is intended for openEuler users who need to manage services and devices. Users must:

      • Know basic Linux operations.
      • Be familiar to configuration of services and devices.

      Bug Catching

      Buggy Content

      Bug Description

      Submit As Issue

      It's a little complicated....

      I'd like to ask someone.


      Just a small problem.

      I can fix it online!

      Bug Type
      Specifications and Common Mistakes

      ● Misspellings or punctuation mistakes;

      ● Incorrect links, empty cells, or wrong formats;

      ● Chinese characters in English context;

      ● Minor inconsistencies between the UI and descriptions;

      ● Low writing fluency that does not affect understanding;

      ● Incorrect version numbers, including software package names and version numbers on the UI.


      ● Incorrect or missing key steps;

      ● Missing prerequisites or precautions;

      ● Ambiguous figures, tables, or texts;

      ● Unclear logic, such as missing classifications, items, and steps.


      ● Technical principles, function descriptions, or specifications inconsistent with those of the software;

      ● Incorrect schematic or architecture diagrams;

      ● Incorrect commands or command parameters;

      ● Incorrect code;

      ● Commands inconsistent with the functions;

      ● Wrong screenshots.

      Risk Warnings

      ● Lack of risk warnings for operations that may damage the system or important data.

      Content Compliance

      ● Contents that may violate applicable laws and regulations or geo-cultural context-sensitive words and expressions;

      ● Copyright infringement.

      How satisfied are you with this document

      Not satisfied at all
      Very satisfied
      Click to create an issue. An issue template will be automatically generated based on your feedback.
      Bug Catching
      编组 3备份