tdb. We should be able to update the ports/databases/tdb to a version Samba 4 likes and point Samba 4 at it. The Samba 3 ports currently does this. Just need to make sure that the 2? other ports using tdb are fine with the update.
Ian McWilliam ________________________________________ From: Jérémie Courrèges-Anglas [[email protected]] Sent: Tuesday, 23 June 2015 8:43 PM To: Ian Mcwilliam Cc: Stuart Henderson; OpenBSD ports Subject: Re: [update] samba-4.1.18 Ian Mcwilliam <[email protected]> writes: > Heimdal comes to mind as an issue. It's not sure to me how things will evolve upstream. On one hand heimdal is embedded in the build system right now, on the other hand there's work being done to get rid of that dependency. Most Linux distros use MIT krb5, not Heimdal, as their main Kerberos implementation. So moving to heimdal from ports right now may not be that interesting in the end. > Post 5.8 would be a good time to resolve these things. Indeed, I don't think pre-5.8 will leave us enough time. [...] >> Lightly tested with --server-role=dc --use-ntvfs and a win7 client. >> Doesn't work with /etc/malloc.conf -> S > > This works fine for my use case (I'm not using AD here, just simple > serving), and actually even with 'S' malloc.conf. With AD I've seen segfaults when joining machines, it looked like the dynamic DNS update step; I haven't looked further. I'm already glad it appears to work for AD auth and netlogon, and for simple file sharing. > Seeing as it isn't hooked up to the build, I don't see any reason > not to update, and with the addition of -as-needed it's hugely more > usable for people building themselves, so OK sthen@. > > With an eye to switching net/samba over to 4.x at some point (which > should be considerably easier than building it in net/samba4 alongside > 3.x in net/samba as the "main" version), it seems sensible to make a > note of any known issues with this: > > - fdm needs a simple tweak in order to find tdb, i.e. > > MAKE_FLAGS= CPPFLAGS="-I${LOCALBASE}/include > -I${LOCALBASE}/include/samba-4.0 -I." There's a more recent, standalone tdb distribution. It's not clear if standalone tdb could be used instead of the bundled one. I'll have to ask upstream. > - needs rc scripts > > - obviously it will need dependencies checking and I imagine in most > cases fixing up to find headers The biggest problems will probably occur at link time. :-/ > - anyone know of anything else? > > I'm thinking that post-5.8 would probably be a good timescale for an > actual changeover. -- jca | PGP : 0x1524E7EE / 5135 92C1 AD36 5293 2BDF DDCC 0DFA 74AE 1524 E7EE
