This is an IBM Automation portal for Cloud Management, Technology Cost Management, Network Automation and AIOps products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
See this idea on ideas.ibm.com
Currently as required by some of the OS hardening best practices, the native /tmp partition of the OS is required to me mounted as 'NOEXEC' .
With this set in place, tacmd update Agent commands, nor installs work on a clean system. It is not possible to remount this partition to EXEC flag , finish patching and renable it always.
And system admins are reluctant to do it on a regular basis.
Hence requesting code adjustment, so that the ITM product can use some variable or a product temp directory something like /opt/IBM/tmp , so that it is self contained, and document this, this way we can force the OS hardening people not to touch the product's temp directory
Idea priority | Urgent |
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.
ITM engineering team recommends cleaning up the old depot location and recreate a new depot after setting the DEPOTHOME to an acceptable location.
From ITM documentation:
If you do not already have an agent depot, the bundles are added to the location defined by DEPOTHOME environment variable in the KBBENV environment fie.
Since the value is empty (DEPOTHOME=), it went to the /tmp directory. By moving it to the new location, the issue should be fixed.