samba - Jan 2015 - Is there any problem that can arise from remapping gidNumber?

This morning I remapped gidNumber from primaryGroupID to gidNumber. I
did that because I could not change the integer in primaryGroupID wit
ldbedt as root.

I mapped to to a new attribute called gidNumber which has no specific
meaning in samba. Is there any potential problems that can arise from
doing that. Is there a better way to fix that problem?

On 13/01/15 11:33, John Lewis wrote:
> This morning I remapped gidNumber from primaryGroupID to gidNumber. I
> did that because I could not change the integer in primaryGroupID wit
> ldbedt as root.
>
> I mapped to to a new attribute called gidNumber which has no specific
> meaning in samba. Is there any potential problems that can arise from
> doing that. Is there a better way to fix that problem?
>
Hmm, definitely going to need more info here, gidNumber has a specific 
meaning to samba, depending on how you set up samba.

Rowland

On 01/13/2015 06:35 AM, Rowland Penny wrote:
> On 13/01/15 11:33, John Lewis wrote:
>> This morning I remapped gidNumber from primaryGroupID to gidNumber. I
>> did that because I could not change the integer in primaryGroupID wit
>> ldbedt as root.
>>
>> I mapped to to a new attribute called gidNumber which has no specific
>> meaning in samba. Is there any potential problems that can arise from
>> doing that. Is there a better way to fix that problem?
>>
> 
> Hmm, definitely going to need more info here, gidNumber has a specific
> meaning to samba, depending on how you set up samba.
>   
> Rowland
> 
I took the defaults except for rfc2307 which I enabled. I am running
Samba Version 4.1.11-Debian.