Re: [mat-dev] Question about initializing a shared MAT installation

["Kevin Grigorenko" <kevin.grigorenko@xxxxxxxxxx>]

It seems that the
answer is that Eclipse will detect that the installation directory is read-only
at startup and use @user.home for the configuration directory: https://help.eclipse.org/latest/index.jsp?topic=/org.eclipse.platform.doc.isv/reference/misc/multi_user_installs.html

I guess this means
that for my internal testing, I should explicitly set the installation
directory to read-only. Alternatively, it seems I can explicitly set -Dosgi.configuration.area=@user.home/.eclipse
to ensure that a user-based configuration directory is used even if the
installation directory is writeable.

--
Kevin Grigorenko
IBM App Platform SWAT




From:
       "Kevin
Grigorenko" <kevin.grigorenko@xxxxxxxxxx>
To:
       "Memory
Analyzer Dev list" <mat-dev@xxxxxxxxxxx>
Date:
       04/19/2021
10:05 AM
Subject:
       [EXTERNAL]
[mat-dev] Question about initializing a shared MAT installation
Sent
by:        "mat-dev"
<mat-dev-bounces@xxxxxxxxxxx>

---

We have a shared MAT installation
accessed through Citrix Windows machines. For example, let's say MAT is
installed in T:\tools\MAT. This directory is not writeable by standard
users. MAT is launched with a batch script like the following which 
We have a shared MAT installation accessed through Citrix Windows machines.
For example, let's say MAT is installed in T:\tools\MAT. This directory
is not writeable by standard users. MAT is launched with a batch script
like the following which specifies a workspace directory which is writable
for that user:

"T:\tools\MAT\eclipsec.exe" -data "%APPDATA%\Memory Analyzer"
-consoleLog -vmargs -Xms1g -Xmx32g

I maintain this tool installation through a git repository and what I've
noticed is that when I update the tool, as I'm testing the new version,
I notice that files are updated in the installation folder (this is after
I've unzipped the MAT installation zip and committed it). For example:

Changes not staged for commit:
  (use "git add <file>..." to update what will be
committed)
  (use "git restore <file>..." to discard changes
in working directory)
        modified:   latest/configuration/org.eclipse.update/platform.xml

Untracked files:
  (use "git add <file>..." to include in what will
be committed)
        latest/configuration/org.eclipse.osgi/151/
        latest/configuration/org.eclipse.osgi/164/0/.cp/META-INF/icons/array_fill.gif
[...]

I noticed that these changes are lazily updated depending on which MAT
functions are exercised.

The issue is that when users are running the tool in the shared environment,
the configuration directory cannot be modified by the user.

I don't know what the potential issues there could be if there are some
files MAT wants to write into this configuration directory and it fails.
I haven't observed anything yet but I don't know if it might cause some
issues.

Are there any recommendations around this? For example, should I exercise
a set of specific functions to generate all of these files before checking
them into the shared environment, or is there a way to specify an alternative
OSGi configuration directory location that would be per-user and would
that be recommended?

Thanks,

--
Kevin Grigorenko
IBM App Platform SWAT
_______________________________________________
mat-dev mailing list
mat-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/mat-dev