Linux-Unix: How S-TAP/GIM processes are initialized by different OS types/versions

When using Upstart servers, the following are the start and stop commands on the Database server:

To stop S-TAP process:

stop utap

To start S-TAP process:

start utap

To stop GIM and supervisor processes:

stop gim_revision#

stop gsvr_revision#

Example, stop gim_46743

To start GIM and supervisor processes:

start gim_revision#

start gsvr_revision#

Example: start gim_46743

To verify status of Guardium product on the system:

initctl list

status utap

When using systemd servers, the following are the commands on the Database server:

To stop S-TAP process:

systemctl stop guard_utap.service

To start S-TAP process:

systemctl start guard_utap.service

To stop GIM and supervisor processes:

systemctl stop guard_gim.service

systemctl stop guard_gsvr.service

To start GIM and supervisor processes:

systemctl start guard_gim.service

systemctl start guard_gsvr.service

To verify status of Guardium product on the system:

systemctl -t service -a|grep guard

When using services servers, the following are the commands on the Database server:

To stop S-TAP process:

svcadm -v disable guard_utap

To start S-TAP process:

svcadm –v enable guard_utap

To stop GIM and supervisor processes:

svcadm –v disable guard_gim

svcadm –v disable guard_gsvr

To start GIM and supervisor processes:

svcadm –v enable guard_gim

svcadm –v enable guard_gsvr

To verify status of Guardium product on the server:

svcs | grep guard