On 29/09/2020 11:59, Ralph Boehme via samba wrote:> Am 9/29/20 um 12:29 PM schrieb Martin Schwenke: >> Don't we need some sort of ID mapping to ensure that IDs are mapped >> consistently across the cluster? > sure, but iirc idmap_tdb (the default) is clustered. > > -slowThen why does the wikipage have these lines: idmap config * : backend = autorid idmap config * : range = 1000000-1999999 Wouldn't it work just as well with: idmap config * : backend = tdb idmap config * : range = 1000000-1999999 My problem with that is, as far as I am aware, tdb is an allocating backend and you cannot ensure that users on each member of the cluster will get the same ID. Rowland
Am 9/29/20 um 1:10 PM schrieb Rowland penny via samba:> On 29/09/2020 11:59, Ralph Boehme via samba wrote: >> Am 9/29/20 um 12:29 PM schrieb Martin Schwenke: >>> Don't we need some sort of ID mapping to ensure that IDs are mapped >>> consistently across the cluster? >> sure, but iirc idmap_tdb (the default) is clustered. >> >> -slow > > Then why does the wikipage have these lines: > > idmap config * : backend = autorid > idmap config * : range = 1000000-1999999 > > Wouldn't it work just as well with: > > idmap config * : backend = tdb > idmap config * : range = 1000000-1999999yes.> My problem with that is, as far as I am aware, tdb is an allocating > backend...yes ...> ... and you cannot ensure that users on each member of the cluster > will get the same ID.... and no. idmap_tdb is using ctdb for the database, so you get clusterwide consistent mappings. -slow -- Ralph Boehme, Samba Team https://samba.org/ Samba Developer, SerNet GmbH https://sernet.de/en/samba/ GPG-Fingerprint FAE2C6088A24252051C559E4AA1E9B7126399E46 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: <http://lists.samba.org/pipermail/samba/attachments/20200929/7df37228/signature.sig>
On 29/09/2020 12:32, Ralph Boehme wrote:> Am 9/29/20 um 1:10 PM schrieb Rowland penny via samba: >> On 29/09/2020 11:59, Ralph Boehme via samba wrote: >>> Am 9/29/20 um 12:29 PM schrieb Martin Schwenke: >>>> Don't we need some sort of ID mapping to ensure that IDs are mapped >>>> consistently across the cluster? >>> sure, but iirc idmap_tdb (the default) is clustered. >>> >>> -slow >> Then why does the wikipage have these lines: >> >> idmap config * : backend = autorid >> idmap config * : range = 1000000-1999999 >> >> Wouldn't it work just as well with: >> >> idmap config * : backend = tdb >> idmap config * : range = 1000000-1999999 > yes. > >> My problem with that is, as far as I am aware, tdb is an allocating >> backend... > yes ... > >> ... and you cannot ensure that users on each member of the cluster >> will get the same ID. > ... and no. idmap_tdb is using ctdb for the database, so you get > clusterwide consistent mappings. > > -slow >OK, I will buy that, so we don't need these lines in the wiki: idmap config * : backend = autorid idmap config * : range = 1000000-1999999 We need these: idmap config * : backend = tdb idmap config * : range = 1000000-1999999 Unless you are running CTDB on a Unix domain member. Rowland