Thanks Don this is checked in, commit e135acefef0ff4512002e2a45c533486158b8cd3. I also fixed it to get the correct value instead of the default 1, commit 94f6e19320036fe06177a74fa71dd5a958aec8f3.
Danny On 03/25/14 15:01, Lipari, Don wrote:
We updated our first machine to 14.03.0 this morning. After the update, I noticed that sshare displayed 0.000 or nan for the FairShare value for every association. The other fields: Raw Shares, Norm Shares, Raw Usage, and Effectv Usage appeared to be ok. I tracked the problem down to an uninitialized damp_factor. When sshare is run, _internal_setup() is not called and damp_factor remains unitialized. The following fixes the problem, though it means that we'll never configure FairShareDampeningFactor to anything other than its default value of 1. Don
