> This all looks correct. You simply have to correctly parse the LDIF
output.
>
> See RFC 2849 for the details. And use a decent LDIF parser for your
favourite
> scripting language and not some home-grown bash/sed/awk/whatever
> scripts which
> fail for such a simple thing.
>
I am not quit
>
> > I hope this makes things clearer.
> > Tell me if I should make an ITS.
>
> That's called "Base64 encoding". Go decode your encoded value, I think
> you'll be happy.
>
The current ldif exports are not encoded, so what should I decode?
The old was, as it should be.
To be more clear:
Wi
I am sorry that I confused you.
I hope this samples make thinks clear:
New Ldif Content:
"dn: cn=hghg,cn=InitialUser,ou=Users,o=caesar
cn: hghg
FileContent:
This is the content of my file. As you can see it is not encoded. Therefor
I can not be imported since ; : blanks,
carriage return etc ar
f the opinion
that this is a bug.
And if you also think this is a bug (and it will be fixed), every other
question is obsolete, since then there is no need for me to migrate the
attributes.
Regards,
Frank
Von:Quanah Gibson-Mount
An: Frank Offermanns ,
openldap-technical@openlda
Build fails for 32 bit msys/mingw (and config --prefix=/mingw
--enable-accesslog --with-tls --enable-syncprov)
slapadd.o: In function `getrec0':
C:/msys/1.0/openldap-2.4.41Git/servers/slapd/slapadd.c:116: undefined
reference
to `ftello'
slapadd.o: In function `slapadd':
C:/msys/1.0/openldap-2.4
Hello,
in our custom schema we have used several attributes with the syntax:
1.3.6.1.4.1.1466.115.121.1.5
attributetype ( myAttributeType:106 NAME ( 'casFileContent' )
DESC 'Contains the file'
SYNTAX 1.3.6.1.4.1.1466.115.121.1.5
SINGLE-VALUE )
We defined this schema befor
Hello Howard,
thank you for your reply.
I use mingw32 and produce 32 bit binaries.
Is it possible that you build/test 64 bit binaries, and that maybe a
preprocessor definition for 32 bit is different from 64 bit?
Regards,
Frank
Von:Howard Chu
An: Frank Offermanns ,
openldap
Hello,
when building the current GIT Version 2.4.40 with Windows and MinGW/MSYS I
get 3 errors:
C:/msys/1.0/openldap-2.4.40git/servers/slapd/slapadd.c:116: undefined
reference
to `ftello'
slapadd.o: In function `slapadd':
C:/msys/1.0/openldap-2.4.40git/servers/slapd/slapadd.c:486: undefined
ref
seems, that I haven't missed such a parameter, so I have to use 64
bit openldap (or use smaller databases).
Best regards,
Frank
Von:Christian Kratzer
An: Frank Offermanns ,
Kopie: Kristoffer Sjögren ,
openldap-technical@openldap.org
Datum: 29.01.2015 14:55
Betreff:Re
,
Frank
Von:Kristoffer Sjögren
An: Frank Offermanns ,
Kopie: openldap-technical@openldap.org
Datum: 28.01.2015 16:32
Betreff:Re: LMDB usage on windows - to much memory needed
Regarding size.
"If an application specifies a size for the file mapping object that is
l
Hello,
we would like to change our backend from hdb to mdb.
I did some initial tests and found out the following:
When setting maxsize to 1.4 GB, the size of the database on the file
system is about 1.4 GB. I thought I read that the maxsize has nothing to
do with the actual physical size needed
Hi,
I have a synrepl-master and one slave.
I delete both databases and do a slapadd on the master.
After doing so I start the slave.
Our system has a few dozen processes changing values every minute, so they
also do it when the inital replication is running.
>From time to time replication stop
slaptest has problems with blanks in pathes:
slapd.conf extraction:
logfile "C:/temp/Blank Dir/log/slapd.log"
...
directory "C:/temp/Blank Dir/accessdata"
slaptest -f "C:\temp\Blank Dir\slapd.conf" -F "C:\temp\Blank Dir\slapd.d"
will succeed when a blank is in the path of "logfile
> > Multimaster only works when slapdadd for initial filling is used with
-w
> > Is this a bug or does it work as designed?
>
> Can't confirm your statement. You need to provide more information about
the
> steps you followed that lead you to this conclusion.
In the thread "delta-syncrepl and
Hi all,
at the end of the thread "Re: delta-syncrepl and mirrormode problem
(2.4.29 and 2.4.30)/ slapadd Usage"
I already asked some questions. But probably due to the wrong threadname I
got no answer.
So here again with a clearer threadname:
Multimaster only works when slapdadd for initial fil
Hello,
now mirrormode with delta-syncrepl seems to work with windows.
The problem was that I added the initial database with slapadd without the
-w option. (slapadd on master 1 and empty master 2)
Is this a bug or does it work as designed?
If it works as designed maybe the manualpage for slapadd
> Sounds like it's having problems with MSYS's fake pathnames, or your
MSYS is
> not mounting filesystems correctly. If you can't fix that, you may be
able to
> workaround this by overriding the test directory using e.g.
>export USER_TESTDIR=C:/msys/1.0/openldap-2.4.30/tests/testrun
Thanks
d still have the same problems.
>
> What's the result from running test063 in the test suite?
> >
> >
> >
> > Frank
> >
> >
> > --
> >
> >
> >
> > Von:Frank Offermanns/CAE
> > An: openldap-technical@openldap.o
Hello Quanah,
I did change my configuration, unfortunately without a change in
behaviour.
I posted this Email at 21.2.2012 to inform you about this :
> Hello Quanah,
> I am double checking my configuration right now.
> > I notice you've configured via slapd.conf, but set up your replication
I tested with 2.4.30 and still have the same problems.
Frank
--
Von:Frank Offermanns/CAE
An: openldap-technical@openldap.org
Datum: 17.02.2012 11:35
Betreff:Re: delta-syncrepl and mirrormode problem (2.4.29)
I wanted to add, that one database is empty when I start and
Hello Quanah,
I am double checking my configuration right now.
> I notice you've configured via slapd.conf, but set up your replication
as
> if you were replicating cn=config, which doesn't really make much sense.
I have no syncrepl - directives in my config-database configured:
I wanted to add, that one database is empty when I start and the other has
only some data. But with master/slave this is no problem, so I think it
should also work for master/master, doesn't it?
I retried with a patched version with these patches:
<
http://www.openldap.org/devel/gitweb.cgi?p=op
Hi,
I want to use delta-syncrepl replication with 2 masters.
But each slapd-process permanently needs about 25 % CPU usage without any
traffic on it.
The log looks endless like this:
** ld 01e43698 Outstanding Requests:
* msgid 55, origid 55, status InProgress
outstanding referrals 0, pa
Since I haven't got an answer to my previous question.
Maybe you could answer me this questions:
In the cases slapd.exe performes internal database cleanup at startup is
it possible for LDAP clients to access
the database while cleanup is running or will connect attempts from
clients fail at t
Hello,
thanks a lot for your info.
> You need to cleanly shut down slapd before rebooting. And/or fix your
init
> scripts to correctly shut down slapd when rebooting.
Due to windows OS i cannot make sure that slapd.exe is not killed, after
40 secs at shutdown every process gets killed.
> Ot
Hello,
I am using OpenLDAP 2.4.25.
After reboot I see logs (Logsetting -d 256) like :
=> bdb_idl_delete_key: c_del id failed: DB_LOCK_DEADLOCK: Locker killed to
resolve a deadlock (-30994)
I checked this and found that I can ignore this.
But one minute after this message OpenLDAP stopped working.
miss a change in the way to build OpenLDAP 2.4.24?
Best regards,
Frank Offermanns
27 matches
Mail list logo
