Dear friend, I saw your post http://lists.samba.org/archive/samba/2008-November/144686.html about running Solidworks with SAMBA as a file server. I'm getting the same issue with the ~files.... Did you solved this issue? Can you explain me how? Thanks, Miki Barzilay
On Sun, Feb 07, 2010 at 11:40:35AM +0200, Miki Barzilay wrote:> Dear friend, > I saw your post > http://lists.samba.org/archive/samba/2008-November/144686.html about running > Solidworks with SAMBA as a file server. > I'm getting the same issue with the ~files.... > > Did you solved this issue? Can you explain me how?The thread ended without us getting the required debug level 10 logs. So we don't know, you might want to contact the initial reporter. Volker -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: Digital signature URL: <http://lists.samba.org/pipermail/samba/attachments/20100208/e46e4dec/attachment.pgp>
2010/2/7 Miki Barzilay <miki at linuxisrael.net>:> Dear friend, > I saw your post > http://lists.samba.org/archive/samba/2008-November/144686.html about running > Solidworks with SAMBA as a file server. > I'm getting the same issue with the ~files.... > > Did you solved this issue? Can you explain me how?In solidworks support they said that using datavault on network drive is not supported and not recommended solution. -- Eero
Quoting Miki Barzilay <miki at linuxisrael.net>:> Dear friend, > I saw your post > http://lists.samba.org/archive/samba/2008-November/144686.html about running > Solidworks with SAMBA as a file server. > I'm getting the same issue with the ~files....We have not got issues with the Solidworks lock files. It is also correct that running Solidworks data on a network drive is not supported by Solidworks. I am suspecting that there may be a permissions issue for your particular share. What we do here is have a user that is used as the owner of the share and a group that everyone who wants to access the share has to be part of. In the config file for that share we have the following settings among others: valid users = @design write list = @design force user = design force group = design read only = No create mask = 0755 directory mask = 06771 HTH, tom