Notice: this Wiki will be going read only early in 2024 and edits will no longer be 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) |
|||
| (3 intermediate revisions by the same user not shown) | |||
| Line 3: | Line 3: | ||
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. | 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 [ | + | See [https://help.eclipse.org/latest/index.jsp?topic=%2Forg.eclipse.platform.doc.isv%2Freference%2Fmisc%2Fruntime-options.html Eclipse multi-user installs] |
| − | + | # Unpack Eclipse Memory Analyzer into a location which can be shared | |
| − | + | # Option: Start MAT and set up preferences etc. as required which will be the default configuration | |
| − | + | # Add the following to MemoryAnalyzer.ini. This stops a root user from running Memory Analyzer and overwriting key files in the shared directories. <br/><code>-protect<br/>root</code> | |
| − | + | # Add to configuration/config.ini a line such as<br/><code>osgi.instance.area=@user.home/MemoryAnalyzer</code><br/>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 | |
| − | + | # Make all the Memory Analyzer files and directories publicly readable, but not writable. | |
| − | -protect | + | # The error logs will go to a location like ~/.eclipse/org.eclipse.mat_1.13.0_87691952_linux_gtk_x86_64/configuration/1651585377771.log The org.eclipse.mat and 1.13.0 come from .eclipseproduct, linux from the os, gtk from ws, x86_64 from arch. |
| − | root | + | |
| − | + | ||
| − | + | ||
[[Category:Memory Analyzer]] | [[Category:Memory Analyzer]] | ||
Latest revision as of 10:43, 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
- Unpack Eclipse Memory Analyzer into a location which can be shared
- Option: Start MAT and set up preferences etc. as required which will be the default configuration
- 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 - 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 - Make all the Memory Analyzer files and directories publicly readable, but not writable.
- The error logs will go to a location like ~/.eclipse/org.eclipse.mat_1.13.0_87691952_linux_gtk_x86_64/configuration/1651585377771.log The org.eclipse.mat and 1.13.0 come from .eclipseproduct, linux from the os, gtk from ws, x86_64 from arch.