[Samba] Inconsistent SYSVOL ACLs

[Anderson Sampaio Mello]

Thanks for the answer.

The path for the two DCs is correct yes, and yes I compiled it for the two
DC servers like this:

./configure --with-systemd --prefix=/usr/local/samba --enable-fhs
make up
make install

After the domain was created, sysvol was created here:

/usr/local/samba/var/lib/samba/sysvol

And the new DC also created sysvol in the same location.

But why samba-tool ntacl sysvolreset cannot restore permissions and these
BUFFER messages appear?

Em dom., 2 de abr. de 2023 às 03:44, Rowland Penny via samba <
samba at lists.samba.org> escreveu:

>
>
> On 02/04/2023 06:02, Anderson Sampaio Mello via samba wrote:
> > I have two domain controller servers, with samba in version 4.18
> >
> > On both DCs both the Sysvol share and the subdirectories (including GPOs)
> > have the same permission:
> >
> > getfacl /usr/local/samba/var/lib/samba/sysvol
>
> You should be using samba-tool to check the permissions, but there
> appears to be something wrong with the path you are using.
> The '/usr/local/samba' seems to suggest that you have compiled Samba
> yourself, but when you do compile Samba, it normally puts sysvol here:
>
> /usr/local/samba/var/locks/sysvol
>
> But most distro Samba packages put it here:
>
> /var/lib/samba/sysvol
>
> You seem to have combined the two.
>
> So, have you compiled Samba yourself ?
> Is the path you are using correct ?
>
> Rowland
>
>
> --
> To unsubscribe from this list go to the following URL and read the
> instructions:  https://lists.samba.org/mailman/options/samba
>