Linux-Unix: How S-TAP/GIM processes are initialized by different OS types/versions
OS | Version | Initialization method | |
---|---|---|---|
AIX | 6.1 | PowerPC | inittab |
AIX | 7.1 | PowerPC | inittab |
AIX | 7.2 | PowerPC | inittab |
HP-UX | 11.11 | pa9000 | inittab |
HP-UX | 11.23 | IA-64 | inittab |
HP-UX | 11.23 | pa9000 | inittab |
HP-UX | 11.31 | IA-64 | inittab |
HP-UX | 11.31 | pa9000 | inittab |
RHEL | 4 | i686 | inittab |
RHEL | 4 | IA-64 | inittab |
RHEL | 4 | x86_64 | inittab |
RHEL | 5 | i686 | inittab |
RHEL | 5 | IA-64 | inittab |
RHEL | 5 | ppc64 | inittab |
RHEL | 5 | s390x | inittab |
RHEL | 5 | x86_64 | inittab |
RHEL | 6 | i686 | upstart |
RHEL | 6 | ppc64 | upstart |
RHEL | 6 | s390x | upstart |
RHEL | 6 | x86_64 | upstart |
RHEL | 7 | ppc64le | systemd |
RHEL | 7 | ppc64 | systemd |
RHEL | 7 | s390x | systemd |
RHEL | 7 | x86_64 | systemd |
SUSE | 11 | i686 | inittab |
SUSE | 11 | ppc64 | inittab |
SUSE | 11 | s390x | inittab |
SUSE | 11 | x86_64 | inittab |
SUSE | 12 | ppc64le | systemd |
SUSE | 12 | s390x | systemd |
SUSE | 12 | x86_64 | systemd |
Ubuntu | 10.04 | x86_64 | inittab |
Ubuntu | 12.04 | x86_64 | upstart |
Ubuntu | 14.04 | x86_64 | upstart |
Ubuntu | 16.04 | x86_64 | systemd |
Solaris | 5.10 | i386 | service |
Solaris | 5.10 | i386_64 | service |
Solaris | 5.10 | SPARC | service |
Solaris | 5.11 | i386_64 | service |
Solaris | 5.11 | SPARC | service |
- Upstart servers
-
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
- Systemd servers
-
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
- Services servers
-
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