Am 2017-10-09 um 20:29 schrieb Rowland Penny:> Unless you have done something strange like giving a group the > gidNumber '3000013', this is an xidNumber and isn't used anywhere > except on a DC. It is also probably one of the Well Known SIDs, so > you shouldn't remove and recreate one of these. Which leads us to > the obvious question, what was the group name ?Actually, it's still there on the DC: # wbinfo --group-info="domain admins" ARBEITSGRUPPE\domain admins:x:3000013: # net cache flush # wbinfo --group-info="domain admins" ARBEITSGRUPPE\domain admins:x:10512: The new and needed group for the particular ACL: # wbinfo --group-info="gfass" ARBEITSGRUPPE\gfass:x:10580: I chose 10850 just to make sure I am away from other IDs. Is there a simple way to read the (highest) used group-id? btw: ACLs work now for the specific folders/ groups, that is not the problem.>> Your reported bug still sits there unnoticed, right? > > Not unnoticed, just not yet resolved ;-)Ah, I see ;-) good.
On Mon, 9 Oct 2017 20:36:15 +0200 "Stefan G. Weichinger" <lists at xunil.at> wrote:> Am 2017-10-09 um 20:29 schrieb Rowland Penny: > > > Unless you have done something strange like giving a group the > > gidNumber '3000013', this is an xidNumber and isn't used anywhere > > except on a DC. It is also probably one of the Well Known SIDs, so > > you shouldn't remove and recreate one of these. Which leads us to > > the obvious question, what was the group name ? > > Actually, it's still there on the DC: > > # wbinfo --group-info="domain admins" > ARBEITSGRUPPE\domain admins:x:3000013: > > # net cache flush > # wbinfo --group-info="domain admins" > ARBEITSGRUPPE\domain admins:x:10512:It isn't supposed to work like this and it didn't used to work like this. I have added this info to the bug report Rowland
Am 2017-10-09 um 21:04 schrieb Rowland Penny via samba:> It isn't supposed to work like this and it didn't used to work like > this.Then the software shouldn't allow me to do so and/or give useful feedback, don't you agree?> I have added this info to the bug reportthanks