Il-2 Dedicated Server mission load problems

[TheGrunch]

Finally solved this problem!

The mission file selection process via file chooser relies upon having network share access to the mission files.

The files were being locked via Samba from the Il-2 SSD client, and therefore when the server came to load them, they were unavailable for reading.

This is strange because the files are not "read" by my program, they are simply selected, so they shouldn't be locked. This may have something to do with opportunistic locking by the Windows Samba client process.

EDIT: Yep, confirmed it. When I add this to my share in my smb.conf it fixes it:

veto oplock files = /*.mis/

[Pfeil]

Good to hear you found the cause, I know bugs that seemingly have no reason to occur are massively frustrating.

Frankly I'm not surprised that you'd run into problems with Windows and Samba. I won't go ranting about it, but ever since Vista the SMB implementation has gotten less and less usable(and don't get me started on file permissions, talk about trading usability for false security).

[TheGrunch]

Tell me about it, apparently the specific reason for this problem is the use of the force user option in samba configuration:

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.