Re: URGENT: 1.3.72 to release this Sunday

Rodney M Dyer wrote:

> At 10:33 AM 10/14/04, Jeffrey Altman wrote:
> It appears from your summary that the only reason this is occuring is 
> because "crypt" is now the default option for OpenAFS clients.  Most 
> people use the default options, so those people are seeing the problem.  
> Our group doesn't use the crypt option (on campus) so our servers are 
> fine.  I'm sure there are many other people who have chosen not to use 
> crypt for whatever reason.  Btw, I'm assuming you mean that Unix/Linux 
> servers are crashing that are running 1.2.11?  We are running the 
> Solaris version of 1.2.11 on all our servers and they seem to be fine, 
> again because we don't enable crypt.

The use of "crypt" is a significant contributing factor.  However,
it is not the cause of the thread safety problems.  There are other
scenarios under which the Windows client can crash.

Another contributing factor I forgot to mention is the Windows client
writing data to AFS.

> I thought you weren't going to release a new version until next year.  

It is not my desire to issue a new release before next year but the
seriousness of this issue is great enough that I will do so.

> Will the 'nix version be updated from 1.2.11 to 1.3.72?

There will certainly be a 1.3.72 release for Unix although it
will not contain the fix for the file server because we do not know
what that is yet.  If you are asking "will 1.3.72 become the stable
release for Unix?"  The answer is "no".

Will we make a patch available for 1.2.11 to solve the problem in
the file servers once we have it?  Yes.

Will we release a 1.2.12 for Unix?  Not my decision.