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

[Neulinger, Nathan]

One other option...=20

Run tethereal (or tcpdump) on your servers, grepping for the volume id /
file id of the data in question. Then let it run for a couple weeks.
Probably would have to custom write a script to do it.

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


> -----Original Message-----
> From: Neulinger, Nathan=20
> Sent: Thursday, April 10, 2003 11:08 AM
> To: Douglas E. Engert
> Cc: Barry Miller; openafs-info@openafs.org
> Subject: RE: [OpenAFS] how can you tell when files in AFS are=20
> no longer accessed.
>=20
>=20
> Well, do you have them on separate volumes?
>=20
> If so, you could at least examine volume access counts over a=20
> few weeks
> to see if they are being used.
>=20
> Won't help you in the case of idle machines though.=20
>=20
> You might consider nmap scanning the list and use the OS Type analysis
> function. From there, you could probably get a useful list of what
> machines are what.
>=20
> -- Nathan
>=20
> ------------------------------------------------------------
> Nathan Neulinger                       EMail:  nneul@umr.edu
> University of Missouri - Rolla         Phone: (573) 341-4841
> Computing Services                       Fax: (573) 341-4216
>=20
>=20
> > -----Original Message-----
> > From: Douglas E. Engert [mailto:deengert@anl.gov]=20
> > Sent: Thursday, April 10, 2003 11:05 AM
> > To: Neulinger, Nathan
> > Cc: Barry Miller; openafs-info@openafs.org
> > Subject: Re: [OpenAFS] how can you tell when files in AFS are=20
> > no longer accessed.
> >=20
> >=20
> >=20
> >=20
> > "Neulinger, Nathan" wrote:
> > >=20
> > > Removing those won't prevent those systems from using=20
> AFS, they just
> > > won't be able to run the commands in /usr/afsws/.=20
> > >=20
> > > We've taken the approach of installing /usr/afsws/ locally on all
> > > systems to avoid having to be concerned about it.
> >=20
> > True, but to get from here to there it would make it easier if we=20
> > could identify the machines that need to be updated.  It=20
> looks like a=20
> > manual process: take the list of clients from the server,=20
> and get the
> > admin to check them.=20
> >=20
> > >=20
> > > The tracing/alert idea sounds like something that would be=20
> > very useful
> > > on the file server. Not sure how much of an impact that=20
> > sort of thing
> > > might have though.
> > >=20
> > > -- Nathan
> > >=20
> > > ------------------------------------------------------------
> > > Nathan Neulinger                       EMail:  nneul@umr.edu
> > > University of Missouri - Rolla         Phone: (573) 341-4841
> > > Computing Services                       Fax: (573) 341-4216
> > >=20
> > > > -----Original Message-----
> > > > From: Barry Miller [mailto:btmiller@anl.gov]
> > > > 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
> > > > longer accessed.
> > > >
> > > >
> > > > We have a bunch of old Transarc AFS architectures installed.
> > > > For example
> > > > alpha_osf32, rs_aix32, sgi_405, sun4_411 among many others.
> > > > Is there any
> > > > way to tell if any clients running these ancient AFS cache
> > > > mangers still
> > > > access our OpenAFS servers? Similarly, is there any way to
> > > > tell when an
> > > > AFS-installed application is still used?
> > > >
> > > > VMS used to let you define an 'alert' ACl to tell you=20
> > when files and
> > > > directories were accessed. Are there any plans to implement
> > > > alert ACLs
> > > > in future OpenAFS release?
> > > >
> > > > Barry Miller
> > > >
> > > > _______________________________________________
> > > > OpenAFS-info mailing list
> > > > OpenAFS-info@openafs.org
> > > > https://lists.openafs.org/mailman/listinfo/openafs-info
> > > >
> > > _______________________________________________
> > > OpenAFS-info mailing list
> > > OpenAFS-info@openafs.org
> > > https://lists.openafs.org/mailman/listinfo/openafs-info
> >=20
> > --=20
> >=20
> >  Douglas E. Engert  <DEEngert@anl.gov>
> >  Argonne National Laboratory
> >  9700 South Cass Avenue
> >  Argonne, Illinois  60439=20
> >  (630) 252-5444
> >=20
> _______________________________________________
> OpenAFS-info mailing list
> OpenAFS-info@openafs.org
> https://lists.openafs.org/mailman/listinfo/openafs-info
>=20