I was exploring a local LDAP solution, as it's for a very large network (1000 sites / 100000 users) we want a disjunction between local administration for machines and global administration for users.
I'll let the tdb solution down anyway Thanks I'll give a feedback on large network architecture as soon as we have finish the deployment. Andrew Bartlett <[EMAIL PROTECTED]>: > On Mon, 2004-03-01 at 23:01, Lapin(c) wrote: > > Hi, > > > > I wonder if it's possible to have multiple backend in order to fragment > SAM > > information. For example, i'd like to have a central LDAP directory for > user > > authentication purpose but a local tdb format for Machines accounts. > > > > I want to minimize network traffic but still keep a central user account > DB. > > > > Has anybody tried this kind of config ? > > This is a really bad idea. The network traffic (LDAP lookups) for > machine accounts really are minimal. If you want to reduce network read > traffic, you might set up a local LDAP slave. > > Get your system working, before you try to create a more complex system. > > Andrew Bartlett > > -- > Andrew Bartlett [EMAIL PROTECTED] > Manager, Authentication Subsystems, Samba Team [EMAIL PROTECTED] > Student Network Administrator, Hawker College [EMAIL PROTECTED] > http://samba.org http://build.samba.org http://hawkerc.net > -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba