s3:torture: use CLI_FULL_CONNECTION_DISABLE_SMB1 in run_oplock_cancel()

Signed-off-by: Stefan Metzmacher <metze@samba.org>
Reviewed-by: Jeremy Allison <jra@samba.org>

diff --git a/source3/torture/test_oplock_cancel.c b/source3/torture/test_oplock_cancel.c
index aa4218a1126e42bff17dc39400deff394383f447..d856650fa23e0808459d4933e16778109bb1bafb 100644 (file)
--- a/source3/torture/test_oplock_cancel.c
+++ b/source3/torture/test_oplock_cancel.c
@@ -113,15 +113,22 @@ bool run_oplock_cancel(int dummy)
        const char *fname = "oplock-cancel";
        uint16_t fnum1;
        NTSTATUS status;
+       /*
+        * Currently this test seems to work only
+        * with SMB2/3 and only against Samba.
+        *
+        * TODO: we should change our server
+        * to ignore cancel for SMB2 Create
+        * and behave like Windows.
+        */
+       int flags = CLI_FULL_CONNECTION_DISABLE_SMB1;
 
-       lp_set_cmdline("client max protocol", "smb3");
-
-       if (!torture_open_connection(&cli1, 0)) {
+       if (!torture_open_connection_flags(&cli1, 0, flags)) {
                return false;
        }
        cli1->use_oplocks = true;
 
-       if (!torture_open_connection(&cli2, 0)) {
+       if (!torture_open_connection_flags(&cli2, 0, flags)) {
                return false;
        }
        cli2->use_oplocks = true;