[OpenAFS] defaults for winclients
Stephen Stoops
Stephen.Stoops@asu.edu
Thu, 17 Jun 2004 12:24:52 -0700
As a newbie at this, I have to ask a stupid question. =20
What do you mean by "Daily Build". Is the 1.3.64 client I downloaded a
few days ago different than the one available today? They both still
say 1.3.6400.
-----Original Message-----
From: openafs-info-admin@openafs.org
[mailto:openafs-info-admin@openafs.org] On Behalf Of Jeffrey Altman
Sent: Wednesday, June 16, 2004 10:34 AM
To: openafs-info@openafs.org
Subject: Re: [OpenAFS] defaults for winclients
Derrick J Brashear wrote:
>On Wed, 16 Jun 2004, Rodney M Dyer wrote:
>
> =20
>
>>The current available client OpenAFS 1.3.6400 has two known issues.
The
>>Freelance option works for most sites, except where your site name is
>>"uncc".
>> =20
>>
>
>Actually I think it's sites where root.afs is (or isn't) some
particular
>volume number. Sites other than uncc had the same problem.
> =20
>
Correct. This problem is fixed in the daily builds.
>>Is has been recently found in testing that the crypt option is
>>problematic on machines where you have P4 hyperthreading enabled. So
from
>>what I gather, unless your site is "uncc" and you are running on a
>>hyperthreaded processor with hyperthreading turned on, you should be
ok
>>with these OpenAFS options.
>> =20
>>
>
>If not having kids but seeing stuff on TV has taught me anything, it's
>that anything "Hyper" is bad. Even the Hypersparc wasn't that great.
> =20
>
This appears to be a locking problem within rx which is being looked
into.
Disabling hyper-threading appears to prevent the bug from being tickled.
- Jeff