> # [11oplocks] > # The Linux kernel does not currently synchronise oplock requests > oplocks = no > level2 oplocks = no The smb.conf man file says that this is a by share setting but I just tried it in the globals section and looks like it works. Disregard all of the fragments I sent.... Another one for inconsistent Samba docs. :)
> > # [12deleteuserscript] > > # Remove Windows Machine Account > > AFAIK samba will not know when a machine leaves a domain. Please explain > how this script is executed? I agree Darrel, I think Samba ignores the call sent by the windows client when it leaves a domain. This script is executed when the machine comes back to the domain (seems a little backwards doesn't it...). For example: MachineA joins the SMEDOMAIN domain and a machine account is create. At some point MachineA leaves the domain to join the SMEWORKGROUP workgroup. At this point, nothing's happened on the Samba server. MachineA's machine account is still "in the system." MachineA then decides to rejoin the SMEDOMAIN domain. When the user authenticates the join, Samba recognizes that MachineA is back but the current server-side machine password for MachineA doesn't match the default password being sent by MachineA. Samba then executes the delete user script parameter followed by the add user parameter. Best regards, Greg Zartman -- 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
