Support for systemd in Linux

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. Now, systemd manages them as unit service files.

To provide systemd support for those services in Linux, the following VCS unit service files and startup scripts are made available:

Old LSB file

New unit service file located at: /usr/lib/systemd/system/

Corresponding script file (SourcePath)

/etc/init.d/amf

amf.service

/opt/VRTSamf/bin/amf

/etc/init.d/gab

gab.service

/opt/VRTSgab/gab

/etc/init.d/llt

llt.service

/opt/VRTSllt/llt

/etc/init.d/vcs

vcs.service

/opt/VRTSvcs/bin/vcs

/etc/init.d/vcsmm

vcsmm.service

/opt/VRTSvcs/rac/bin/vcsmm

/etc/init.d/vxfen

vxfen.service

/opt/VRTSvcs/vxfen/bin/vxfen

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.