Kevin Bedford wrote: > Jeremy Allison wrote: >> On Wed, Jul 09, 2008 at 10:14:23AM +1000, Kevin Bedford wrote: >>> Hi all, >>> >>> There are many posts on many lists about this issue but no >>> definitive answers. >>> >>> For me the issue came up with a new server running CentOS 5 + samba >>> 3.0.35c + openldap. >>> >>> The recent postings I've seen always seem to have either RHEL 5 or >>> CentOS 5 in common with the provided 2.6.18 kernel. >>> >>> The issue is .doc or .xls files saving and then producing an error >>> about not being able to open the file for writing. Then it claims >>> the file is locked by the user who just saved the file. It even >>> occurs in users own home directories where no one else could have >>> opened the file >>> >>> I've tried disabling kernel locks, oplocks, level2 oplocks, create >>> mode =0660 and >>> socket options = TCP_NODELAY IPTOS_LOWDELAY SO_KEEPALIVE >>> SO_RCVBUF=8192 SO_SNDBUF=8192 >>> >>> All of which have been listed somewhere as fixes but do not help. >>> I've been searching for a solution for nearly two months now. >>> >>> Can someone please tell me what it is???? >> >> Are you using ACLs on the drive ? If so, this is a bug with ACL >> inheritance I've fixed for 3.0.30. Thanks >> >> Jeremy. > > Thanks Jeremy, > > Not intentionally mostly because I don't know how but I guess > upgrading to 3.0.30 would fix it either way. > > Can you suggest a good source of info on the ACLs with Samba topic? > > Thanks again > > Kevin
Set force security mode = 0770 in the problematic share. This fix the bug... at least, works for me. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba