Date: Wed, 14 Jun 2017 22:56:16 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 219999] net/samba46 net/samba45 net/samb43 unable to install as AD/DC Message-ID: <bug-219999-13@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219999 Bug ID: 219999 Summary: net/samba46 net/samba45 net/samb43 unable to install as AD/DC Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: Individual Port(s) Assignee: timur@FreeBSD.org Reporter: dgilbert@eicat.ca Assignee: timur@FreeBSD.org Flags: maintainer-feedback?(timur@FreeBSD.org) Back some time ago, I met with all the errors I met with this week trying to install samba* as an AD/DC at home. At the time, my solution was to use net/samba42 ... as that worked. Rolling forward, ACLs of various and several sorts prevent us from running = the "samba-tool domain provision" script. I can neither find any viable work arounds nor can I forge any myself. This ACL problem is true of both ZFS and UFS2. I tested UFS2 separately wi= th Posix and NFSv4 ACL. I tested ZFS with many different combinations of it's= ACL settings. The directory in question defaults to /var/db/samba4/private. If you are testing this bug, creating a partition for /var/db/samba4 is sufficient. I tested this with FreeBSD-11-STABLE, but I don't see anything here that I suspect is FreeBSD-version specific. In writing this, I realize that there may be some large amount of work here= .=20 At the very least, the port should be marked... not BROKEN per se ... it st= ill works as a non-AD/DC, AFAIK, but marked (maybe in the summary text at the e= nd of the build) as being broken in this use to save other people the time and frustration. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-219999-13>