On Wed, 17 Oct 2001, Bruce L. Friedman wrote:
> Now, I did some testing, and I see the problem is completely based on > the one little line: > > oplocks = no > > in the [global] section of smb.conf in SME V5 ... > When I modified smb.conf on SME V5 to remove the line, the delay was > gone. Yes, oplocks can be a big performance win. But as discussed previously, the performance gain can be at the cost of data reliability. > My simple understanding is that samba will still protect windows users > from collisions on these files, but not other users (local, NFS, > appletalk...). Not exactly the whole truth. Samba will sort out contests for file access between windows clients, but it won't ensure that other local users get up to date files, and it won't protect windows clients from other changes to files that they might never see. > Since I am not using NFS, and not doing anything with these files > locally on the SME server, is it safe to remove this line from smb.conf?> As long as you also don't have appletalk clients, and don't use ftp, then yes, you should be able to safely make the change. Charlie Brady [EMAIL PROTECTED] Lead Product Developer Network Server Solutions Group http://www.e-smith.com/ Mitel Networks Corporation http://www.mitel.com/ Phone: +1 (613) 368 4376 or 564 8000 Fax: +1 (613) 564 7739 -- 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
