From 053d6c605caebf5ed61b86f320da6a35f0c5257f Mon Sep 17 00:00:00 2001 From: Andrew Tridgell Date: Wed, 21 Oct 1998 00:31:14 +0000 Subject: at the interop Isaac (at least I _think_ it was Isaac) said that if a MS client doesn't respond to a oplock break request then we might try resending the request. This morning Sues Win95 machine had this problem (thus forcing me to do something about it!). When starting winword her box refused to answer an oplock break request. I have added code to resend the oplock break request up to 3 times at 10 second intervals before killing the socket. of course, as soon as I did this her box started to behave again so I haven't been able to tell if this fix actually works, but it can't be worse than dropping the socket immediately. (This used to be commit a1c4d8351b9171416693e6d7a9045bdce9217edb) --- source3/include/local.h | 4 ++++ 1 file changed, 4 insertions(+) (limited to 'source3/include') diff --git a/source3/include/local.h b/source3/include/local.h index 7c63ab830b..85e61c63c4 100644 --- a/source3/include/local.h +++ b/source3/include/local.h @@ -184,6 +184,10 @@ #define OPLOCK_BREAK_TIMEOUT 30 +/* how many times do we try to resend the oplock break request - useful + for buggy MS clients */ +#define OPLOCK_BREAK_RESENDS 3 + /* Timout (in seconds) to add to the oplock break timeout to wait for the smbd to smbd message to return. */ -- cgit