That was my thought too, but I'd hard-code a sunset on using the technique. Pick a date beyond which we just skip the test so clients quit doing it, and that wart can be removed from the source any time thereafter.
On 12/16/2010 11:51 AM, Steve Simmons sent: > Having read the entire discussion up to this point, I find the alternate > version 3404 to be an acceptable workaround. There are lots of things in > various bits of software which look around for condition X to see if Y is > acceptable. Lacking a proper solution (more on that in a separate note), this > seems quite reliable. > > Derrick notes it's dicey software release and engineering; yeah, I agree. So > let's comment the crap out of it in the code. > > Summary: go for it. > > Steve > > _______________________________________________ > OpenAFS-info mailing list > [email protected] > https://lists.openafs.org/mailman/listinfo/openafs-info -- +--------------------------------------------------------------+ / [email protected] 919-445-9302 http://www.unc.edu/~utoddl / / Those who jump off a Paris bridge are in Seine. / +--------------------------------------------------------------+ _______________________________________________ OpenAFS-info mailing list [email protected] https://lists.openafs.org/mailman/listinfo/openafs-info
