Re: [Samba] FreeBSD-11 and Samba-4.6 as a DC
- Date: Sun, 16 Jul 2017 09:38:43 +0100
- From: Rowland Penny via samba <samba@xxxxxxxxxxxxxxx>
- Subject: Re: [Samba] FreeBSD-11 and Samba-4.6 as a DC
On Sun, 16 Jul 2017 17:36:02 +1000
Dewayne Geraghty <dewayne.geraghty@xxxxxxxxxxxxxxxxxxxxxxx> wrote:
> James, David,
> You will not be able to provision SAMBA 4.6 on FreeBSD. Refer to:
> https://bugzilla.samba.org/show_bug.cgi?id=12730 2017-04-04 13:49:39
> UTC which is the same result that James and I are experiencing.
> Nothing to do with NFS and nothing to do with the deprecated and
> unused ntvfs.
> I am running SAMBA 4.6.6 Standalone on an i386 FreeBSD 11.1Prerelease
> and a SAMBA 4.5.12 AD on amd64 FreeBSD11.1 Prerelease.
> I spent a few hours trying to determine the problem but gave up.
> Someone with greater familiarity to the code and appreciate for Python
> will need to take up the reins.
> Admittedly I was distracted by a debug level 5 or higher as it
> complained of not being able to find the administrator, which led me
> to pam.d/login issues. Similarly the debug displayed use_ntvfs which
> was in fact a variable within the Python code, set to false. A
> standard FreeBSD build is all that's required to provision a SAMBA
> 4.5.12 AD.
The problem seems to be with extended attributes not ACLs. I initially
thought it was an ACL problem, mainly because that was what the error
message seemed to show. What I cannot understand is, why does it work
on 4.5.x but not on 4.6.x, the only real difference between the code is
that the 'ntvfs' server is no longer built by default on 4.6.x.
As soon as I get chance, I will build the latest in the 4.5.x series
and see if I can get this to provision.
To unsubscribe from this list go to the following URL and read the