Guillaume Rousse <[EMAIL PROTECTED]> writes:
> Hello list.
>
> I'm looking for a way to reduce information duplication in an LDAP
> directory, using the equivalence of joint in SQL databases. Basically,
> all my user entries (inetorgperson + posixAccount) need to have a
> 'secretary' and a 'manage
Dieter Kluenter a écrit :
> Guillaume Rousse <[EMAIL PROTECTED]> writes:
>
>> Hello list.
>>
>> I'm looking for a way to reduce information duplication in an LDAP
>> directory, using the equivalence of joint in SQL databases. Basically,
>> all my user entries (inetorgperson + posixAccount) need to
Hi all,
I ve been trying to add an new custom objectclass
(ndsLoginProperties) and i m always getting this error. Anyone can
decipher it?
Oct 24 17:12:31 ldap slapd[79408]: bdb_referrals: op=104
target="cn=NDS,ou=Policies,dc=example,dc=com"
matched="ou=Policies,dc=example,dc=com"
Oct 24 17:12:3
Dear list
Is it possible (or already some openldap extension to) do
sort-without-articles?
Example is: "The Ritz-Carlton" should be listed before "TAVRIDA ELECTRIC
AG" but actually the current sorted search result gives "TAVRIDA
ELECTRIC AG" first. Usually "The" should be removed in ordering.
Ha
--On Wednesday, October 24, 2007 5:21 PM +0800 Benny Chee
<[EMAIL PROTECTED]> wrote:
Hi all,
I ve been trying to add an new custom objectclass
(ndsLoginProperties) and i m always getting this error. Anyone can
decipher it?
Oct 24 17:12:31 ldap slapd[79408]: bdb_referrals: op=104
target="cn=
Benny Chee wrote:
> Oct 24 17:12:31 ldap slapd[79408]: conn=14 op=1 RESULT tag=105 err=64
> text=naming attribute 'cn' is not present in entry
See http://www.openldap.org/faq/data/cache/1006.html
Ciao, Michael.
I'm not aware of such a feature, but extending slapo-valsort to do this
shouldn't be too difficult.
On Wed, 24 Oct 2007, Zhang Weiwu wrote:
Dear list
Is it possible (or already some openldap extension to) do
sort-without-articles?
Example is: "The Ritz-Carlton" should be listed before "TAVRI
Guillaume Rousse <[EMAIL PROTECTED]> writes:
> Dieter Kluenter a écrit :
>> Guillaume Rousse <[EMAIL PROTECTED]> writes:
>>
>>> Hello list.
>>>
>>> I'm looking for a way to reduce information duplication in an LDAP
>>> directory, using the equivalence of joint in SQL databases. Basically,
>>> all
Michael Ströder writes:
>Benny Chee wrote:
>> Oct 24 17:12:31 ldap slapd[79408]: conn=14 op=1 RESULT tag=105 err=64
>> text=naming attribute 'cn' is not present in entry
>
> See http://www.openldap.org/faq/data/cache/1006.html
Actually RFC 4511 (section 4.7) changed such an Add request to be valid
On 10/23/07 5:15 PM, Howard Chu wrote:
Francis Swasey wrote:
I'm sorry I haven't gotten back to you on this before now.
I've done some testing and I need a pointer or two to see if I've got
something wonky or a bug.
On my master server, the accesslog overlay has a contextCSN value for
the acce
--On October 24, 2007 3:22:21 PM -0400 Francis Swasey
<[EMAIL PROTECTED]> wrote:
Please post your configs.
--Quanah
--
Quanah Gibson-Mount
Principal Software Engineer
Zimbra, Inc
Zimbra :: the leader in open source messaging and collaboration
I don't know what is the problem, but with your suggestion should run well,
but it doesn't.
I have tried both ways.
My LDAP server is:
dc=tel,dc=uva,dc=es
cn=root
ou=users
uid=dpercam(GID=1002)
uid=caralo(GID=1001)
ou=groups
cn=profesores(gidNumber
Hi Sorry Dieter,
I have been trying to redo everything from the beginning, and now I
have got everything right except the same problem. Here is the error
which slapadd generates:
>>> dnPrettyNormal:
<<< dnPrettyNormal: ,
str2entry: invalid value for attribute clientorg (syntax
1.3.6.1.4.1.1466.
13 matches
Mail list logo