Antw: Re: Q: monitoring attributes

2013-11-27 Thread Ulrich Windl
Dieter Klünterdie...@dkluenter.de schrieb am 27.11.2013 um 10:34 in Nachricht 20131127103401.4123c...@pink.avci.de: Am Wed, 27 Nov 2013 09:09:35 +0100 schrieb Ulrich Windl ulrich.wi...@rz.uni-regensburg.de: Hi! I found out why I never was successful with cn=monitor: By default '*'

Antw: Re: Q: monitoring attributes

2013-11-27 Thread Ulrich Windl
Dieter Klünterdie...@dkluenter.de schrieb am 27.11.2013 um 11:15 in Nachricht 20131127111527.0e561...@pink.avci.de: Am Wed, 27 Nov 2013 09:09:35 +0100 schrieb Ulrich Windl ulrich.wi...@rz.uni-regensburg.de: Hi! I found out why I never was successful with cn=monitor: By default '*'

Re: Antw: Re: Q: monitoring attributes

2013-11-27 Thread Howard Chu
Ulrich Windl wrote: BTW: I noticed that there is no schema for entryCSN neither... See doc/drafts/draft-chu-ldap-csn-xx.txt -- -- Howard Chu CTO, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP

Re: Antw: Re: Q: monitoring attributes

2013-11-27 Thread Howard Chu
Ulrich Windl wrote: Dieter Klünterdie...@dkluenter.de schrieb am 27.11.2013 um 11:15 in In fact spaces in a commonName attribute value are in accordance with X.520 practice. Hi! I believe that, but when printed two spaces look very similar to one space, and as I guess every space is

Re: Antw: Re: Q: monitoring attributes

2013-11-27 Thread Michael Ströder
Howard Chu wrote: Ulrich Windl wrote: BTW: I noticed that there is no schema for entryCSN neither... See doc/drafts/draft-chu-ldap-csn-xx.txt This is one of those things a generic LDAP client has to be prepared to handle with some fall-back mechanism. You can enable this hidden experimental