Tell me about it, apparently the specific reason for this problem is the use of the force user option in samba configuration:
Quote:
|
Samba includes an smb.conf parameter called force user that changes the user accessing a share from the incoming user to whatever user is defined by the smb.conf variable. If oplocks is enabled on a share, the change in user access causes an oplock break to be sent to the client, even if the user has not explicitly loaded a file.
|
Oh well! At least now I know this is not a bug in my code and can start working on the mission cycle scheduler.
