 | ||
| About managing VCS modules | ||
|---|---|---|
| Prev | VCS configuration concepts | Next |
The initialization daemon of the operating system manages the start, stop, restart, and status of the AMF, GAB, LLT, VCS, and VxFEN modules. The service files and the script files for these modules are deployed at the appropriate location at the time of installation. Table: Unit service files and script files for systemd support lists these files and their locations.
systemd is an initialization system that controls how services are started, stopped, or otherwise managed on RHEL 7 and SLES12 or later systems. The LSB files for the VCS stack have been replaced with the corresponding systemd unit service files. In the older RHEL distributions, the init.d daemon managed the related services. In newer RHEL distributions, systemd manages them as unit service files.
The following VCS unit service files and startup scripts help provide systemd support for those services in Linux:
Table: Unit service files and script files for systemd support
To start, stop, restart, or view the status of one of these services, use the following command:
systemctl [start | stop | restart | status] unitServiceFile
Note: |
The status option of the systemctl command displays only the status of the unit service file, like whether it is active, inactive, or failed. |
To view the actual status information about the module or to view the HAD status, use:
serviceSourceScript status
For example:
/opt/VRTSvcs/bin/vcs status
To view the source path of any service, you can use the systemctl command as follows:
# systemctl show unitServiceFile -p SourcePath
For example:
# systemctl show vcs -p SourcePath
The systemctl command displays the source path as follows:
SourcePath=/opt/VRTSvcs/bin/vcs
Wherever systemd support is available, all the process in the VCS stack start in system.slice instead of user.slice.