[OpenAFS] cache performance

[Neulinger, Nathan]

That might be a good idea, but I would say that the subagent in that
case would be a client to whatever services the file server provides.
You wouldn't want to hook that into the fileserver itself in this case
without a pretty hefty security audit.=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: Lawrence Greenfield [mailto:leg+@andrew.cmu.edu]=20
> Sent: Wednesday, October 30, 2002 11:57 AM
> To: openafs-info@openafs.org
> Subject: Re: [OpenAFS] cache performance
>=20
>=20
>    From: Phil.Moore@morganstanley.com
>    Date: Wed, 30 Oct 2002 12:49:26 -0500
> [...]
>    I think a better mechanism would be to have the fileserver maintain
>    this information in memory, and to query it (and reset it)
>    periodically, via a new RPC.  Then, I can ask for this=20
> data as often
>    as I want, once a day, or maybe once an hour, if I need to do finer
>    grained analysis.
>=20
> I've had some success instrumenting applications to return performance
> related information via SNMP. This makes it easy to integrate those
> applications with existing monitoring/graphing applications.
>=20
> Normally I do this by creating a Net-SNMP agentx subagent.
>=20
> The major downside (of course there's a downside or three!) is that
> SNMP security isn't widely deployed (and the most widely deployed
> varieties are damn annoying).
>=20
> Larry
>=20
>=20
> _______________________________________________
> OpenAFS-info mailing list
> OpenAFS-info@openafs.org
> https://lists.openafs.org/mailman/listinfo/openafs-info
>=20