[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: Different output with ldapsearch



On Thursday 29 March 2007, Amos Castelli wrote:
> Hi all,
> can anybody tell me if the following is a bug or is a normal behavior?
> $ ldapsearch -x -H ldap://ldap.ex.com -b ou=People,dc=ex,dc=com |grep
> zhiling $ ldapsearch  -x -H ldap://ldap.ex.com -b ou=People,dc=ex,dc=com
> "(uid=zhiling)"
>
> # extended LDIF
> #
> # LDAPv3
> # base <ou=People,dc=ex,dc=com> with scope subtree
> # filter: (uid=zhiling)
> # requesting: ALL
> #
>
> # zhiling, People, ex.com
> dn: uid=zhiling,ou=People,dc=ex,dc=com
> uid: zhiling
> cn: Uela Zhiling
> objectClass: account
> objectClass: posixAccount
> objectClass: top
> loginShell: /usr/local/bin/bash
> uidNumber: 20893
> gidNumber: 30484
> homeDirectory: /users/zhiling
> gecos: Uela Zhiling, DCS
>
> # search result
> search: 2
> result: 0 Success
>
> # numResponses: 2
> # numEntries: 1
>
>
> why I don't get any match with the grep command?

The most likely answer is that your first search exceeded it's size or time 
limit before finding the entry. Unfortunately, you don't provide the result 
code from the first search (which would have told you the answer anyway).

Regards,
Buchan

-- 
Buchan Milne
ISP Systems Specialist - Monitoring/Authentication Team Leader
B.Eng,RHCE(803004789010797),LPIC-2(LPI000074592)

Attachment: pgpfB7WkIYERd.pgp
Description: PGP signature