The fglam process never appears to stop when trying to shut it down with fglam -q or using the Quest supplied rc/init script. The FglAM logs suggest the shutdown was completed successful.
When doing a truss on the process, the process constantly tries to open /tmp/.com_ibm_tools_attach/_master
When FglAM was started as a different user, e.g. root, from what is now running as so the permissions on the /tmp/.com_ibm_tools_attach/_master file (used by the Java Attach API) do not allow it to be opened.
[1] Kill the FglAM and Quest Watchdog processes with kill -9
[2] Change the permissions on the relevant files to allow the new user to modify them:
chmod -R a+rwx /tmp/.com_ibm_tools_attach
FglAM should not be able to start and shut down without any problems.
© ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center