From: Brent Callaghan (Brent.Callaghan@eng.sun.com)
Date: 09/29/98-06:41:13 PM Z
Date: Tue, 29 Sep 1998 15:41:13 -0800 (PDT) From: Brent Callaghan <Brent.Callaghan@eng.sun.com> Subject: Re: locking errors Message-ID: <Roam.1.1.907108873.21953.brent@jurassic> On Tue Sep 29, Carl Beame wrote: > My hope is that by adding routines which allow the sysadmin to > determine the names of the locked files, the last access time by the > particular client etc will make (1) above the more workable solution > then it is today, As I mentioned before, you could configure your server to grant reaaallly looonng lock leases and have a sysadmin answering the phone calls for lock unstick requests. Neither does leased locks stop you from providing a tool that'll identify locks and blow them away. You can tune your server's lock removal for "fully automatic" or fully manual. > I mean that the client tells the server what lease time to use for > locks. If this is not allowed I don't want to use leases. It's better that the server control the lease time since the length of the lease is based on variables such as server reboot time, server load, server use of NV storage for lock info, etc. Why should the client choose the lease ? Generally it has no idea how long it needs to hold a lock. Brent
This archive was generated by hypermail 2.1.2 : 03/04/05-01:46:26 AM Z CST