[bug-notifications] [samba_common 0001805]: Samba fails to work correctly with smbpasswd and tdbsam backends, standalone server
Mantis Bug Tracker
noreply at opencsw.org
Thu Feb 23 15:25:47 CET 2012
The following issue has been CLOSED
======================================================================
https://www.opencsw.org/mantis/view.php?id=1805
======================================================================
Reported By: buysse
Assigned To: dam
======================================================================
Project: samba_common
Issue ID: 1805
Category: other
Reproducibility: always
Severity: block
Priority: normal
Status: closed
Resolution: open
Fixed in Version:
======================================================================
Date Submitted: 2006-09-19 15:00 CEST
Last Modified: 2012-02-23 15:25 CET
======================================================================
Summary: Samba fails to work correctly with smbpasswd and
tdbsam backends, standalone server
Description:
There are known issues as posted on the samba lists with 3.0.23b in
standalone configurations, especially with the traditional smbpasswd
backend.
I just set a new box with s10u2 and the current samba package, and I could
not get it to work no matter how I hacked at it (both smbpasswd and tdbsam
backends, connections just didn\'t complete and smbd processes took a kill
-9 to restart).
Can you push a 3.0.23c in to testing and I\'ll check whether the issues are
still there? Obviously, it\'s a recommended upgrade either way - 3.0.23b
lasted less than a week before another patch was released.
For the new server, I backed off to an earlier release from stable, with
the same configuration, and had no problems.
======================================================================
----------------------------------------------------------------------
(0009648) dam (administrator) - 2012-02-23 15:25
https://www.opencsw.org/mantis/view.php?id=1805#c9648
----------------------------------------------------------------------
This should be fixed in 3.6.1,REV=2012.01.05.
More information about the bug-notifications
mailing list