Lars: If you have a reproducible test case, please follow the directions in the release notes and file a bug report to [EMAIL PROTECTED]In particular, if you can place a live public test case that I can run a client against it will make things much easier to track down.
Also, I would really like to understand the rationale for creatinga link that includes either ".." or "../..". Can you provide me an example where this makes sense?
The limit of 100 characters seems very strange. The max length of a target is 1024 characters.
Thank you. Jeffrey Altman Lars Richter wrote:
Hello all, we get some serious problems with file links in our environment.We are using OpenAFS for Windows version 1.5.30 and Linux AFS-Servers 1.4.6.When we create a file link under Linux with a pattern like "PATH/../../PATH" and the path is longer than 100 characters, we get an error on Windows "Permission denied". In a 64bit environment the AFS-Client crashes with a message "OpenAFS Stopping due to error (cm_scache.c:1783): cm_scache_t refCount 0." in the EventLog.I did some tests with older versions. The result is, that the latest version without the error is 1.5.21. I think, there is a problem in the recursion detection feature in version 1.5.22, which was partly fixed in 1.5.23 and 1.5.24.Does the path have a pattern like "PATH/../PATH" there are no problems. Does anyone have any suggestions? Regards, Lars
smime.p7s
Description: S/MIME Cryptographic Signature
