Rolandas Naujikas wrote:
We have been used OpenAFS 1.3.77 on Windows Terminal Server 2003, and
it's working stable, when there works only one. But when many (~20)
students with homes on AFS are trying use this server, then sometimes
(randomly) access to AFS stops (early versions with hung on each access
to files, now with access denied).
I'm interested in debug this, but I'm limited in time. I can send (post)
debug output from afsd*.log, but it is not easy reproduce.
You don't have to debug it. Run the debug version of the installer
and when the problem occurs attach windbg.exe to it and capture a full
dump file. Place the dump file somewhere that I can access it. Make
sure it is secure because it will contain all of the private info of
the cache, tokens, etc. I will debug it.
P.S. Sorry for not be able support the efforts to improve code, but I
have too much work.
I'm not sympathetic. We all have too much work. If you are going to
rely on an open source technology and its community to provide services
to your end users, then you should find the time to help. This is
my personal opinion and I know there are others here that disagree with
me.
Jeffrey Altman
smime.p7s
Description: S/MIME Cryptographic Signature
