wine users - Jul 2010 - Multiple instances of wine on different machines with $HOME on NFS

Hi,

we're running wine on a number of Linux machines
which get their $HOME via a NFS server.

In particular, we have a windows commandline program 
(a data format converter for mass spectrometers, not that it matters) 
things work fine as long as I am running only one instance of wine.

If I have several wine instances on different boxes 
running in parallel, they seem to corrupt the registry.

I have not found anyone with a similar problem, let alone a fix.
I might have to copy a temporary .wine into /tmp 
and use $WINEPREFIX in a per-machine specific manner.

Or is there some easier way ? 

Yours,
Steffen

P.S.: 
I'll append the following snippet to
http://wiki.winehq.org/HomeDirectoryOnNFS
once it is operational again:

Apart from performance problems, you might encounter problems
with .NET2.0 if your C: drive lives on a network,
e.g. a "NFS System.IO.FileLoadException: Failed to
grant minimum permission requests." failure.

The reason is that .NET2.0 by default considers everything coming from
the network as possibly tainted. Usually you can issue something like
"CasPol.exe -m -ag 1.2 -url file://... FullTrust" command 
to make e.g. your intranet trusted.

Unfortunately CasPol.exe is living on C:, and is not trusted 
if that is served via NFS ... If you still want C: to be on NFS 
(despite the above mentioned performance penalty),
the fix is to copy your CasPol.exe to a local directory, and use 
wine /tmp/CasPol.exe -m -ag 1.2 -url "file:///c:\\*" FullTrust 


-- 
IPB Halle                    AG Massenspektrometrie & Bioinformatik
Dr. Steffen Neumann          http://www.IPB-Halle.DE
Weinberg 3                   http://msbi.bic-gh.de
06120 Halle                  Tel. +49 (0) 345 5582 - 1470
                                  +49 (0) 345 5582 - 0
sneumann(at)IPB-Halle.DE     Fax. +49 (0) 345 5582 - 1409

Steffen Neumann wrote:
> Hi,
>
> we're running wine on a number of Linux machines
> which get their $HOME via a NFS server.
>
> In particular, we have a windows commandline program 
> (a data format converter for mass spectrometers, not that it matters) 
> things work fine as long as I am running only one instance of wine.
>
> If I have several wine instances on different boxes 
> running in parallel, they seem to corrupt the registry.
>
>   
Known bug.  You are using and modifying the same registry file no matter 
where the users are connecting from.

You will have to install Wine on each user's machine and then install 
the applications there (much like you would in Windows).

Then you can use something like Samba to connect to the central server 
for file services.

The above is outside the Wine project.

Using winecfg you can map the Samba mount point to a Wine drive.

James McKenzie