Web lists-archives.com

Re: [Samba] FreeBSD-11 and Samba-4.6 as a DC

On Fri, 14 Jul 2017 04:36:08 +1000
Dewayne Geraghty <dewayne.geraghty@xxxxxxxxxxxxxxxxxxxxxxx> wrote:

> Thanks Rowland.  I think I've narrowed down the issue to being
> extended attributes, not posix ACL's as the cause.

I agree, run the provision with -d10 and out pops:

store_acl_blob_fsp: storing blob length 320 on file /usr/local/samba/var/locks/sysvol
store_acl_blob_fsp: setting attr failed for file /usr/local/samba/var/locks/sysvolwith error Invalid argument
set_nt_acl_no_snum: fset_nt_acl returned NT_STATUS_INVALID_PARAMETER.

> To clarify
> 1. lets take NFS out of scope, as ufs with posix acl's does, I
> believe, achieve the same functionality regarding ACL's as ext4.  I
> have no interest in NFSv* except that it has a richer command set for
> ACL's and I "thought" that would be preferred.  It isn't preferred
> and its probably more to do with inconsistent implementation methods
> across OS'. 

You are probably correct.

> 2. I didn't want to use ntvfs, only that it was
> something I recognised in the python traceback.  Having rebuilt a
> samba 4.6.6 with ntvfs, and still failed to provision, we can rule
> that out.  And I can remove the deprecated functionality out of my
> samba.

I only mentioned 'ntvfs' because using it seems to have been the only
way to get a Samba AD DC on Freebsd.

> I've lodged a PR with the FreeBSD folks that should assist James'
> issue regarding bhyve and samba provisioning.
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220712

I was just trying to provision Samba as usual, no jail or chroot and I
get the same problem.
The cause seems to be an incorrect blob size, no idea what size it
should be.


To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba