--On Wednesday, June 24, 2009 10:13:13 AM -0400 Sean O'Malley
<[email protected]> wrote:
But while I am thinking about upgrades and migrations is there a way to
determine client versions that are connecting, who is using them and what
ip they are connecting from?
Sure. You can use rxdebug against your fileservers to see what clients
currently have connections, and/or send them SIGXCPU (SIGPOLL on HPUX) and
look at the hosts.dump file. Then you can use rxdebug -version against
each of those clients to find out what version they are.
If there is an upgrade from 1.4 -> 1.5 or 1.6 and client version 1.2 isn't
supported
Yeah, we generally don't do that. If you want to keep running afs3.2
clients (and still have a platform they'll run on), we'll feel sad for you,
but it should still work.
A customizable auto-reply message system would be the most ideal, like a
log, popup window and/or email message on their end to nag them a bit.
- client too new and unsupported planned upgrade on xyz date
- client unsupported will be deprecated on xyz date
- client deprecated.
- feature xyz unsupported will be by xyz date.
- you are a security risk.
- your client causes data and hair loss
Yup, that would be neat, but not as a feature of OpenAFS. AFS is a
filesystem, not a customer communication tool.
-- Jeff
_______________________________________________
OpenAFS-devel mailing list
[email protected]
https://lists.openafs.org/mailman/listinfo/openafs-devel
