fcntl F_SETLKW64

[Romeril, Alan]

> > Why is the break from the client taking so long to arrive?
> 
> Don't know. I've always wondered why Windows clients take so long
> to do things with oplocks sometimes. Client bugs would be my guess
> (sometimes they don't answer them at all).
> 
> Did the smbd process waiting for the break to return time out ?
> (ie. did you get the "oplock_break: client failure in oplock break"
> message ?).
> 

Yes it did time out, yes that was the massage I saw.


Also the fcntl F_SETLKW64 bug is still there I have just had to pkill
the smbds AGAIN as the load ave hit 50.
machine:bash-2.04#truss -p 13162
fcntl(7, F_SETLKW64, 0xFFBEF7B0)                = 0
fcntl(7, F_SETLKW64, 0xFFBEF7B0)                = 0
fcntl(7, F_SETLKW64, 0xFFBEF7B0)                = 0
fcntl(7, F_SETLKW64, 0xFFBEF820)                = 0
kill(29956, SIG#0)                              = 0
fcntl(7, F_SETLKW64, 0xFFBEF7B0)                = 0
fcntl(7, F_SETLKW64, 0xFFBEF7B0)                = 0
fcntl(7, F_SETLKW64, 0xFFBEF7B0)                = 0
fcntl(7, F_SETLKW64, 0xFFBEF820)                = 0
fcntl(7, F_SETLKW64, 0xFFBEF7B0)                = 0

again yes Solaris 8, on an Ultra

Alan