On Mon, Jun 25, 2018 at 11:08:45AM -0300, Gleydson Soares wrote:
> On Mon, Jun 25, 2018 at 08:49:31AM +0200, Landry Breuil wrote:
> > On Mon, Jun 25, 2018 at 02:25:40AM -0300, Gleydson Soares wrote:
> > > unbreak ldapd regress,
> > > everything seems to be working fine.
> >
> > the point of the ov
On Mon, Jun 25, 2018 at 08:49:31AM +0200, Landry Breuil wrote:
> On Mon, Jun 25, 2018 at 02:25:40AM -0300, Gleydson Soares wrote:
> > unbreak ldapd regress,
> > everything seems to be working fine.
>
> the point of the overly complicated grep line was to handle the case
> where you have a running
On Mon, Jun 25, 2018 at 02:25:40AM -0300, Gleydson Soares wrote:
> unbreak ldapd regress,
> everything seems to be working fine.
the point of the overly complicated grep line was to handle the case
where you have a running production ldapd, and you spawn another one for
regress.. that's also why i
unbreak ldapd regress,
everything seems to be working fine.
;;x250 ~/src/regress/usr.sbin/ldapd> make ; echo $?
configuration ok
ldapsearch -x -H ldapi://%2ftmp%2fldapi | diff -
/home/gsoares/src/regress/usr.sbin/ldapd/out/empty.log
ldapsearch -x -p 6639 -h localhost 2>&1 | diff -
/home/gsoares/
