ldapd(8) binary incompatibility, 5.4 - 5.5

2014-07-22 Thread Matthew Weigel
I finally upgraded my last machine - that runs ldapd(8) for user logins, mail aliases, and a few other odds and ends - from 5.4 to 5.5. I'm left wondering if I'm the only one who actually uses the stock ldapd(8), because it is not called out at all in upgrade55.html as having problems with the

Re: ldapd(8) binary incompatibility, 5.4 - 5.5

2014-07-22 Thread Olivier Mehani
On 2014-07-22, Matthew Weigel uni...@idempot.net wrote: I finally upgraded my last machine - that runs ldapd(8) for user logins, mail aliases, and a few other odds and ends - from 5.4 to 5.5. Haha! I just did the same two days ago. I'm left wondering if I'm the only one who actually uses the

Re: ldapd(8) binary incompatibility, 5.4 - 5.5

2014-07-22 Thread Matthew Weigel
On 7/22/14, 9:03 PM, Olivier Mehani wrote: I ended up having to create a 5.4 VM (I stuck with the same amd64 arch as my actual server, and have not investigated or tested under what constraints this might work across architectures) to load the ldapd(8) database files, use third party LDAP tools

Re: ldapd(8) binary incompatibility, 5.4 - 5.5

2014-07-22 Thread Matthew Weigel
On 7/22/14, 9:37 PM, Matthew Weigel wrote: into it, I started up ldapd(8) and connected to it with ldapvi(1) from ports. I wrote out the contents of that buffer to a separate file, and Actually I didn't notice it this weekend but ldapvi(1) has --in and --out arguments that do exactly the

Re: ldapd(8) binary incompatibility, 5.4 - 5.5

2014-07-22 Thread Olivier Mehani
Hey Matthew, On 2014-07-23, Matthew Weigel uni...@idempot.net wrote: into it, I started up ldapd(8) and connected to it with ldapvi(1) from ports. I wrote out the contents of that buffer to a separate file, and Actually I didn't notice it this weekend but ldapvi(1) has --in and --out