We have a commercial application we've been running for years on an
openafs-1.4.14 client on a RedHat Linux box. This week we upgraded the
client to 1.6.9, but quickly had to revert. The difference has to do with
file locking. The section of strace output below shows the behavior in the
old
On Thu, 17 Jul 2014 10:07:07 -0400
Todd Lewis todd_le...@unc.edu wrote:
Was there some change in file locking semantics that would make sense of
this? Does this application tickle a corner case error in openafs's file
locking, or does more rigorous lock handling in the newer client expose a
On Thu, 17 Jul 2014 10:07:07 -0400
Todd Lewis todd_le...@unc.edu wrote:
Was there some change in file locking semantics that would make sense
of this? Does this application tickle a corner case error in openafs's
file locking, or does more rigorous lock handling in the newer client
expose a
Andrew,
The suggested patch was applied, installed, and our application now works
correctly again with the new client.
Thank you very much for your timely response. Looking forward to this
patch making its way to release soon.
--
todd_le...@unc.edu
On 07/17/2014 11:59 AM, Andrew Deason
Todd,
unless there's a problem found with it, this patch will be part of the next
ordinary stable release.
Thanks a lot for reporting your problems with 1.6 and reporting back on the
proposed fix. And Kudos to Andrew for whipping that up so swiftly.
Stephan
On Jul 17, 2014, at 21:20
