Adam Megacz wrote: > Jeffrey Altman <[EMAIL PROTECTED]> writes: >> Then you will want to upgrade to 1.4.1-rc7 when it is available. > > Ok, cool. > > BTW, regarding the whole hacking-it-versus-submitting-bugs, under > normal circumstances, and wrt future issues, I totally agree with you. > This was an unusual situation that had the potential to go a long way > towards getting OpenAFS adopted here. In hindsight, it was a bad > choice on my part, although I have to say that I'm still mystified why > 1.4.1rc6-Tiger as worked so incredibly well for me on my primary > machine but seems to cause trouble for others. > > I also think the subject line made it seem like I was asking for a > feature request rather than a pointer or two to the right places in > the code so I could build one custom copy of the client as a > short-term fix. > > - a
You are not using this code in a vacuum. Many other people are working with the same code and experience the same problems. The gatekeepers are not sitting still quietly twiddling our thumbs. We receive bugs reports, gather evidence, reproduce the conditions, and fix the problems with the assistance of the community. The reason that your faculty are having problems are you are not is because the problem they are seeing is not in the client but in the server and their usage pattern triggers it and yours does not. That is why it is important to gather information and post a report that is as complete as possible. Then those in the community who have been suffering the same issues can speak up and either provide assistance or fill in the gaps so that the real problem can be narrowed down. What were you going to do with a private build that was hacked to set the Hard Dead Timeout value to 5 seconds instead of 120 seconds? Were you going to give it to the faculty member to install on her/his machine? In my opinion that would have been a disaster since the reliability of the client would have gone down the tubes and the user would have completely given up. 1.4.1-rc7 has now been tagged in the repository. Source code tarballs and MacOS X and Windows installers will be on the web site by morning. If after installing the new file server you are still experiencing problems, bump the log level to 125, capture several hours worth of activity and then file a bug report. Someone will examine the file log entries to figure out what is going on. Jeffrey Altman
smime.p7s
Description: S/MIME Cryptographic Signature
