This documentation is no longer maintained and may contain obsolete information. You should instead refer to https://github.com/CAST-Extend/com.castsoftware.aip.console.tools for more information about automating source code delivery/analysis with AIP Console.
When using the CAST Delivery Manager Tool command line interface in a Linux environment and when multiple Linux users are being used, care must be taken to ensure that the optional -logFilePath option is handled correctly:
When the -logFilePath option is not defined in the command line, a default path for the log will be used as follows:
- When the DMT is operated for the first time by user A, the log file directory structure is automatically created by the tool under /tmp. The new directories are owned by user A with access rights rwx------, i.e. only A can access these directories. The DMT will function correctly.
- If the DMT is then operated by user B, the DMT will try to access the default log file path under /tmp as user B, however, user B has no access rights to the path, therefore the DMT will fail because it cannot write to the log file path.
There are several options that can be used to avoid this issue:
- Ensure that the -logFilePath option is always defined in the command line - this will ensure that the DMT will always be able to write to the log file regardless of the user that is used.
- If it is not possible to define a -logFilePath and you want to rely on the Linux default log file location under /tmp there are several options available:
- Set a custom TMPDIR environment variable for the each user that will be using the DMT, for instance /tmp/UserA instead of just /tmp
- At the end of each command line execution, remove the /tmp/.CAST directory and its content so that it will be created again when a different user uses the DMT
- Grant rwx access rights on the whole directory structure starting at /tmp/.CAST to the new user