I do use it, though, at it works fine mostly. I've heard it explained
that the reasoning for avoiding TDBSAM is that if you're running a PDC,
you probably also need features not provided by TDBSAM. In many cases,
that isn't exactly accurate. We have MANY users, but our needs are
fairly simple
All, I have a site with around 200 concurrent users, with a user count of
over a thousand... I'm currently using just one PDC using the smbpasswd
backend. I currently do not want to go into an LDAP backend... but would
tdbsam be a better alternative?
One of the issues I have is, pretty randomly,
According to the Samba documentation, smbpasswd is not even recommended
for a PDC...
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba
I was asking the same question not too many days ago.
I went with LDAP. It is not as difficult as some people think. It seems
somewhat daunting at first but then you quickly get the grasp of it.
It simply *works* and solves *a lot* of challenges at the same time,
leaving you ready for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I think you want tdbsam. There's virtually no downside.
=R
Aaron Souza wrote:
All, I have a site with around 200 concurrent users, with a user count of
over a thousand... I'm currently using just one PDC using the smbpasswd
backend. I currently
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Miguel Medalha wrote:
According to the Samba documentation, smbpasswd is not even recommended
for a PDC...
I do use it, though, at it works fine mostly. I've heard it explained
that the reasoning for avoiding TDBSAM is that if you're running a PDC,
