[OpenAFS] who has that file open

Neulinger, Nathan nneul@umr.edu
Thu, 1 Dec 2005 13:13:13 -0600

"file locking" is not just around the corner... It has always been
there, and has always worked fine...  If you're meaning "byte range
partial file locking", then yes, that is in the current release
candidate for windows only, and is purely client side.

At best, you could determine who has callbacks against particular files,
but not whether they have the file open. Callbacks are based on if the
file is in the cache, not whether it's open.=20

Now, you could determine if the file is open *AND* locked, but most file
operations do not lock the file. Additionally, well behaved apps will
keep files locked for as short a period of time as required for the use

-- Nathan

Nathan Neulinger                       EMail:  nneul@umr.edu
University of Missouri - Rolla         Phone: (573) 341-6679
UMR Information Technology             Fax: (573) 341-4216

> -----Original Message-----
> From: openafs-info-admin@openafs.org=20
> [mailto:openafs-info-admin@openafs.org] On Behalf Of David Bear
> Sent: Thursday, December 01, 2005 10:34 AM
> To: openafs
> Subject: [OpenAFS] who has that file open
> since file locking is 'just around the corner' for openafs (at least
> I'm hopeful) the question I have now is will (is) there be a way to
> ask the server who has a particular file open. the afs server has to
> keep track of which client has a file open in order to force the cache
> manager to do its callback functions correct? If so, there should be a
> way to query the afs server to see who has fileX open.
> This would be a really nice feature...
> --=20
> David Bear
> phone: 	480-965-8257
> fax: 	480-965-9189
> College of Public Programs/ASU
> Wilson Hall 232
> Tempe, AZ 85287-0803
>  "Beware the IP portfolio, everyone will be suspect of trespassing"
> _______________________________________________
> OpenAFS-info mailing list
> OpenAFS-info@openafs.org
> https://lists.openafs.org/mailman/listinfo/openafs-info