Hi, I'm setting up a new Samba server, and am debating between LDAP (complex, and I'm not that familiar with it) and tdbsam for the password backend... I understand the physical limitations (single PDC, no replication, etc), which is fine, since this is a small office - about 50 workstations, possibly growing to as many as 75, but no more than that. What are the limitations of the tdbsam backend, with respect to performance and the number of workstations/users it can reasonably be expected to support? The box itself is a Tyan MB/dual opteron 280 with 2GB of RAM (can add more RAM if needed)... Thanks! -- Best regards, Charles
Charles Marcus, on 12/21/2007 8:06 AM, said the following:> What are the limitations of the tdbsam backend, with respect to > performance and the number of workstations/users it can reasonably be > expected to support?Never mind - of course this is well documented in the most excellent 'The Official SAMBA-3 HOWTO and Reference Guide'... For anyone curious - it is not generally recommended to use the tdbsam backend for sites with 250+ users, but this is only because these sites likely will be spread out and require BDCs and multiple servers... They specifically mention one site using the tdbsam backend with 4,500+ users with no performance problems whatsoever... Sorry for the noise. -- Best regards, Charles
Possibly Parallel Threads
- tdbsam.
- Hi I am vinod, I want to set up simple Samba PDC using tdbsam password backend. samba is installed on fedora 8 GNU/Linux. my network is about 30 windowsXP Pro. SP-2 static IP addressed machines. total no users about : 40 my network is : 192.168.1. sa
- central PDC + remote BDCs: LDAP strategy, my lack of comprehension
- Samba PDC, ldap or mysql????
- Samba3-beta1 as a PDC and using tdbsam as passdb backend it takes the home-directory info from /etc/passwd