Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "MemoryAnalyzer/Shared Installation"
(Initial page) |
|||
Line 9: | Line 9: | ||
2. Option: Start MAT and set up preferences etc. as required which will be the default configuration | 2. Option: Start MAT and set up preferences etc. as required which will be the default configuration | ||
− | 3. Add to MemoryAnalyzer.ini | + | 3. Add the following to MemoryAnalyzer.ini. This stops a root user from running Memory Analyzer and overwriting key files in the shared directories. |
+ | <nowiki> | ||
-protect | -protect | ||
− | root | + | root</nowiki> |
− | 4. Make all the Memory Analyzer files and directories publicly readable, but not writable. | + | 4. Add to configuration/config.ini a line such as |
+ | <nowiki> | ||
+ | osgi.instance.area=@user.home/MemoryAnalyzer</nowiki> | ||
+ | This sets the workspace as the default would be under the Memory Analyzer install directory, so would not be writable. This means the user does not have to specify -data | ||
+ | |||
+ | 5. Make all the Memory Analyzer files and directories publicly readable, but not writable. | ||
[[Category:Memory Analyzer]] | [[Category:Memory Analyzer]] |
Revision as of 09:11, 3 May 2022
Sometimes it can be useful to install Eclipse Memory Analyzer in a shared directory so that many people can use it, but ideally with their own settings.
See [Eclipse multi-user installs](https://help.eclipse.org/latest/index.jsp?topic=%2Forg.eclipse.platform.doc.isv%2Freference%2Fmisc%2Fruntime-options.html)
1. Unpack Eclipse Memory Analyzer into a location which can be shared
2. Option: Start MAT and set up preferences etc. as required which will be the default configuration
3. Add the following to MemoryAnalyzer.ini. This stops a root user from running Memory Analyzer and overwriting key files in the shared directories.
-protect root
4. Add to configuration/config.ini a line such as
osgi.instance.area=@user.home/MemoryAnalyzer
This sets the workspace as the default would be under the Memory Analyzer install directory, so would not be writable. This means the user does not have to specify -data
5. Make all the Memory Analyzer files and directories publicly readable, but not writable.