My apologies to the list. 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?
If there is an upgrade from 1.4 -> 1.5 or 1.6 and client version 1.2 isn't supported, then it would be nice to contact the user/system admin before the upgrade. 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 My apologies to the list if this exists and I just missed it. On Tue, 23 Jun 2009, Jeffrey Hutzelman wrote: > --On Tuesday, June 23, 2009 09:10:45 AM -0400 Sean O'Malley > <[email protected]> wrote: > > > If this is enabled, then the server piece needs to be stable and > > bulletproof. In otherwords, make the server bulletproof, and you can fix > > the clients later. > > No, that's not at all what Derrick said. In fact, generally server-side > problems are much easier to fix, because even when you control all the > clients, you don't control all the clients. But that point's moot, because > the feature we're talking about here is a server implementation feature and > doesn't affect clients. > > -- Jeff > _______________________________________________ > OpenAFS-devel mailing list > [email protected] > https://lists.openafs.org/mailman/listinfo/openafs-devel > -------------------------------------- Sean O'Malley, Information Technologist Michigan State University ------------------------------------- _______________________________________________ OpenAFS-devel mailing list [email protected] https://lists.openafs.org/mailman/listinfo/openafs-devel
