Dear list,
I personally think this is a non-issue, but I may be incorrect. If it is a non issue I need to find a way to get some communication going on making it evident to the devlopers of a software program.
I have strict locking = YES (which is by default set to NO) set
and I have been repeatedly told that there is a locking issue within SAMBA. I don't believe this is the case as we are pushed towards a propriatary client.
Basically it boils down to this...
1.) Samba has been stable...no/few issues
2.) Locking is set to strict...shouldn't have the issues that COMPANY X and COMPANY Y had right?
3.)Why do I want to pay thousands of dollars because COMPANY X and COMPANY Y couldn't figure out that locking should be set.
Now what I'm asking if:
A.) Is this locking issue is indeed resolved by me setting this lock?
B.) Even if that setting resolves said issue or not - what can I do to get some communication open for testing so we don't have to purchase X product because of a simple fix or setting change. I'd be more than happy to get ahold of some developers at this place to get some kind of a dialog set up. It _should_ be in their best intrest to get interoprability going with samba as we aren't the only customer running it with thier products.
The following message is from a developer at the software company...
=========================================================================
From an UNIX / NT interoperability point of view, it is correct that the
solutions we have evaluated are NFS clients that can be installed on
Windows, in order to access data from UNIX server through NFS. The 2
solutions we have evaluated are Hummingbird NFS Maestro and Intergraph
Disk Access (also available through MS Services For UNIX).
We are not recommending the use of Samba based solutions : you report a
data corruption issue at <COMPANY X>; I have been on my side reported data corruption issue at <COMPANY Y> with Samba based solutions. These 2 issues added to the fact that Samba solutions do not support NFS locking
interoperability are enough not to recommend such solutions.
What is documented corresponds to what we have successfully evaluated
and what we could recommend a customer to evaluate if looking for an UNIX/NT interoperability solution (we also recommend customers to verify that these tools match their own constraints (from a security, performance, ..., points of view). If a customer reports a problem specific to one of these tool, we would be able to provide some support as we have this software available for problem determination, but in the case the problem was in the NFS client itself (and not in CATIA code), we would not be able to provide direct support on these tools are they are third party components, supported by their respective vendors.
I hope this answers your question.
Regards,
