Guardium STAP process does not start when "init q" is issued and /etc/inittab line is too long on some Operating Systems

Resolving The Problem

To resolve the issue one of the following actions can be taken. 1) is preferred ..

1) - uninstall the product and install into a shorter directory name - eg the default directory /usr/local

OR

to make a soft link - for example

ln -s  /usr/local/guardium_v82_r57354_1/guardium/guard_stap/guard_tap.ini /var/guard_tap.ini

edit the /etc/inittab accordingly - wit the /var/guard_tap.ini at the end instead of the original long directory/path/file

utap:2345:respawn:/usr/local/guardium_v82_r57354_1/guardium/guard_stap/guard_stap  /var/guard_tap.ini

start the STAP with init q

vmguard6:~ # init q

The STAP process can be checked by for example

vmguard6:~ # ps -ef | grep -i tap
root      6275     1 94 15:22 ?        00:00:01 /bin/bash -f /usr/local/guardium_v82_r57354_1/guardium/guard_stap/guard_stap /var/guard_tap.ini
root      6296  4031  0 15:22 pts/0    00:00:00 grep -i tap


By using a soft link - this will allow the original guard_tap.ini file to be amended manually or via GIM as normal - and have those changes reflected in the linked file - hence no extra maintenance would be needed on the linked file .