New samba not starting

[COLLOT Jean-Yves]

Hi.

That's my fault. For performance reasons, I changed the default Samba/VMS
option for "oplocks" to "No".

I must admit I don't clearly understand what those oplocks are and what they
are supposed to do. I just saw that when enabled, they add activity of IP
messages between the smbd processes on the VMS server, and the overall
performance is worst. I know that the Samba documentation claims that "The
oplock code can dramatically (approx. 30% or more) improve the speed of
access to files on Samba servers". In my experience, it may be true on Unix,
but it's not true on VMS. 

If I'd known better, I would have changed the "level2 oplocks" default to
"No" too, in order to avoid the warnings in TESTPARM. I'll do it for the
next release.