Winbindd in Large Installations
goetz.rieger at suse.de
Mon Dec 10 01:16:04 GMT 2001
we are evaluating a server consolidation involving Samba/Winbindd. The
main goal is migrating a couple (~40) OS/2 fileservers to virtual
Linux-Servers on S/390 running Samba. As a central authentication
instance a W2K PDC in going to be used. The userbase is about ~950
We definitely don´t want to maintain a second user database. So I think
our best guess is winbindd, which I used in a small installation and
which I found pretty impressing. But here some questions are coming to
- Does anybody use winbindd in a larger productive environment?
- Is there any way to get a consistent user/ID mapping with winbindd
(ja, I read the manual) over several Samba servers? Something like "tell
winbindd to fetch all user/groups on startup" or distribute a predefined
- Has anybody experience with the management of the memoryleak mentioned
in the release notes?
- Losing the database with the user/ID mapping would be a disaster. Is
there any problem with backing up and re-using the (tdb?)-files?
And apart from winbindd:
- What is the status of quotas in 2.4.x? Any improvements in newer
Every hint and tip would be appreciated.
More information about the samba-ntdom