"strict locking = no" sounds like a very good approach to me which I would prefer over the way that I use it at the moment (still E-smith 4.1.2, Samba 2.2.1a, test server):
With "oplocks = yes" I got also rid of that error message when logging off (all versions of Win2k: no SP, SP1 and SP2) but "oplocks = yes" in the global settings might create other problems (as discussed recently) so I kept "oplocks = no" (the E-smith default) in the global settings and use "oplocks = yes" only for that particular profile share: [profiles] comment = Windows (NT, 2000) Profiles path = /home/e-smith/files/winprofiles/ guest ok = no read only = no writable = yes oplocks = yes printable = no create mode = 0660 force create mode = 0660 directory mode = 0770 force directory mode = 0770 It's another way that seems to work here but I believe if "strict locking = no" works, it's a better solution. Regards, Michael Doerner > I had the same problem initially, but if you set "strict locking = no" in > smb.conf, it ends this problem. I don't know if it breaks anything else, > but I haven't noticed any adverse effects. > > > One glitch however - I want to use roaming profiles saved to the users > > home directory but I get this error when I log the user off/shutdown. > > > > "Windows cannot update your roaming profile. Contact your network > > administrator. > > DETAIL: The process cannot access the file because another process has > > locked a portion of the file" > -- 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
