On Mon, 19 Jun 2000 mark.muhlestein@netapp.com wrote:
<cut>
As to the protocol issues, as Bruce said, we're more or less stuck with them because of Microsoft compatibility. If a session goes away when there is no request pending (i.e. we don't owe the client a response), the filer delays 10 minutes before terminating the session. This is to keep the session alive in the face of temporary network partitions, which we can't distinguish from just losing a client. Currently that 10 minute interval is not configurable on the filer, but it sounds like we might want to make it so.
This 10 minute timeout doesn't seem to be working. I tried this with my PC yesterday. It had approx 13 locks, I turned the power off, and after an hour the filer still thought the locks were active. However they have gone this morning, after around 16 hours. We're running 5.3.5.
-- Dave Atkin, Head of Technical Services Computing Service, University of York, YORK YO10 5DD Phone: +44-1904-433804 (ddi) Fax: +44-1904-433740 Email: D.Atkin@york.ac.uk