Gordon Rowell <[EMAIL PROTECTED]> said:
> We were advised to disable oplocks by a lead member of the Samba team as
> i-bays enable concurrent updates from Samba, FTP and Appletalk. We also
> had an instance of file corruption at a client site which appeared to
> be rectified by disabling oplocks.
The current e-smith approach where oplocks = no is the 'safe' approach.
It is a simple matter to create a templates-custom/11oplocks and change
this to oplocks = yes. Bear in mind that many older, but widely used
database and accounting programs do not support opportunistic locking and
file caching. If oplocks is enabled, these programs will corrupt their
databases during multiple user access.
This is not a Linux only issue. Even under W2K Server oplocks and file
caching must be disabled in the registry for some programs to work. As
an example this is mandatory for Accpac for DOS.
I believe the e-smith way is the correct default. As I've mentioned
above it is easy to change. Just make sure you know why you are doing
this and the potential consequences of turning oplocks on.
Regards,
--
Darrell May
DMC NETSOURCED.COM
http://netsourced.com
http://myEZserver.com
--
Please report bugs to [EMAIL PROTECTED]
Please mail [EMAIL PROTECTED] (only) to discuss security issues
Support for registered customers and partners to [EMAIL PROTECTED]
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org
