Displaying 4 results from an estimated 4 matches for "ldb_sqlite".
2018 Jul 13
1
A few questions and propostions on the samba architecture
...gt; stuff like server side transparent password token validation.
> >
> > Depending on my undarstanding of the current architecture and the
> > state of the ldb sqlite backend this would seem like the easiest
> > approach, correct me if I'm too far off.
>
> Using ldb_sqlite wouldn't help, as we don't use it in a smart way, it
> was added (and then left unmaintained, we really should remove it) in
> the hope of getting transaction support, but instead that was gained
> via tdb.
>
> The uidNumber and gidNumber changes you desire are reasonable, a...
2018 Jul 13
5
A few questions and propostions on the samba architecture
Due to a few problems I encountered I had a tiny look at the samba code
and gut a few questions, statements and propositions. Please by all
means, correct me if I got something wrong.
1. besides filestore for shares and config files samba uses ldb as an
exclusive storage backend
1. LDB supports TDB, LDAP and SQLITE3 backend
2. Samba hard codes to TDB files like
2018 Jul 13
0
A few questions and propostions on the samba architecture
..." to implement fancy stuff
> like server side transparent password token validation.
>
> Depending on my undarstanding of the current architecture and the state
> of the ldb sqlite backend this would seem like the easiest approach,
> correct me if I'm too far off.
Using ldb_sqlite wouldn't help, as we don't use it in a smart way, it
was added (and then left unmaintained, we really should remove it) in
the hope of getting transaction support, but instead that was gained
via tdb.
The uidNumber and gidNumber changes you desire are reasonable, and we
could do those in t...
2018 Jul 13
3
A few questions and propostions on the samba architecture
...fancy stuff
>> like server side transparent password token validation.
>>
>> Depending on my undarstanding of the current architecture and the state
>> of the ldb sqlite backend this would seem like the easiest approach,
>> correct me if I'm too far off.
> Using ldb_sqlite wouldn't help, as we don't use it in a smart way, it
> was added (and then left unmaintained, we really should remove it) in
> the hope of getting transaction support, but instead that was gained
> via tdb.
>
> The uidNumber and gidNumber changes you desire are reasonable, an...