ParaView-5.8.0-MPI-Linux-Python3.7-64bit tries to write to /var/tmp/OptixCache -- why?
Currently testing Paraview 5.8.0 (ParaView-5.8.0-MPI-Linux-Python3.7-64bit) on a visualization cluster with multiple users. The binary works for the first user who launches paraview; when this happens, a directory is created in /var/tmp/OptixCache with the ownership being the user who launched the binary. Afterwards, when a different user tries to launch the same binary, it fails because they don't own (or have access to) /var/tmp/OptixCache. Changing permissions for /var/tmp/OptixCache fixes this problem but we want to know if collisions might result if more than one user runs paraview at the same time.
Also, is there any way to control the behavior of the writing location (e.g. write to a different directory other than /var/tmp/OptixCache for example $HOME for each user)?