Red Hat Bugzilla – Bug 147983
Update RHEL samba version to 3.0.11
Last modified: 2012-06-20 11:56:49 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5)
Description of problem:
Please update the RHEL 3.0 samba component set to 3.0.11 as soon as
possible. The 3.0.11 release provides file locking fixes that severely
affect our ability to maintain file modified date/time attributes on
Excel files accessed through Samba.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. View the file's "modified" date/time stamp
2. Open the Excel file, close the file (without saving)
3. The "modified" date/time changes to the current date/time, even
though the file has not been changed/updated.
Expected Results: The modified date/time stamp should not change when
a file is opened and closed without saving.
I performed testing for the Samba group to verify that the
file-locking issue (which is the root cause of the problem described)
was resolved in 3.0.11.
The modified date stamp is relied upon heavily here by the Engineering
Internal RFE bug #147999 entered; will be considered for future releases.
I've made an unofficial, not-officially-supported build of
Samba-3.0.11 for RHEL3 avaliable at
Please try it and report whether it solves your problems. If it
does, I can try to get it included in a future update release.
Your unofficial, not-officially-supported build of Samba-3.0.11 for
RHEL3 solves the file-locking problem we were having. Please convert
this to an official patch release whenever possible.
Thanks for your time and efforts!
The next fixed issue should be high load caused by nmbd so it's worth
to upgrade to 3.0.11, see:
Thank you for submitting this issue for consideration in Red Hat Enterprise Linux. The release for which you requested us to review is now End of Life.
Please See https://access.redhat.com/support/policy/updates/errata/
If you would like Red Hat to re-consider your feature request for an active release, please re-open the request via appropriate support channels and provide additional supporting details about the importance of this issue.