[OpenAFS] how can you tell when files in AFS are no longer accessed.

[Neulinger, Nathan]

Removing those won't prevent those systems from using AFS, they just
won't be able to run the commands in /usr/afsws/.

We've taken the approach of installing /usr/afsws/ locally on all
systems to avoid having to be concerned about it.

The tracing/alert idea sounds like something that would be very useful
on the file server. Not sure how much of an impact that sort of thing
might have though.=20

-- Nathan

------------------------------------------------------------
Nathan Neulinger                       EMail:  nneul@umr.edu
University of Missouri - Rolla         Phone: (573) 341-4841
Computing Services                       Fax: (573) 341-4216


> -----Original Message-----
> From: Barry Miller [mailto:btmiller@anl.gov]=20
> Sent: Wednesday, April 09, 2003 1:08 PM
> To: openafs-info@openafs.org
> Subject: [OpenAFS] how can you tell when files in AFS are no=20
> longer accessed.
>=20
>=20
> We have a bunch of old Transarc AFS architectures installed.=20
> For example=20
> alpha_osf32, rs_aix32, sgi_405, sun4_411 among many others.=20
> Is there any=20
> way to tell if any clients running these ancient AFS cache=20
> mangers still=20
> access our OpenAFS servers? Similarly, is there any way to=20
> tell when an=20
> AFS-installed application is still used?
>=20
> VMS used to let you define an 'alert' ACl to tell you when files and=20
> directories were accessed. Are there any plans to implement=20
> alert ACLs=20
> in future OpenAFS release?
>=20
> Barry Miller
>=20
> _______________________________________________
> OpenAFS-info mailing list
> OpenAFS-info@openafs.org
> https://lists.openafs.org/mailman/listinfo/openafs-info
>=20