Hi all,
I do the following testing, use a running "ftp" to instead of existed LDAP, and with its corresponding port, # ldapsearch -x -H ldap://192.168.123.1:22 Here, 192.168.123.1 is a ftp server with port 22 open.
When I execute the command, it seems to be hung without any error messages.
I think, if the ldap server or port is not available, it would return with error message immediately.
How do you think of this interesting testing?
Regards, Phillip
--On Thursday, November 02, 2006 7:53 PM +0800 Phillip phuang@plasmon.cn wrote:
Hi all,
I do the following testing, use a running "ftp" to instead of existed LDAP, and with its corresponding port, # ldapsearch -x -H ldap://192.168.123.1:22 Here, 192.168.123.1 is a ftp server with port 22 open.
When I execute the command, it seems to be hung without any error messages.
I think, if the ldap server or port is not available, it would return with error message immediately.
How do you think of this interesting testing?
I think you are having ldapsearch talk to an open port running a different protocol, and ldapsearch is likely waiting for a protocol specific response, since the port is open. I think your "test" is rather odd. Of course, if you specified a timeout to ldapsearch, I bet it'd stop hanging.
--Quanah
-- Quanah Gibson-Mount Principal Software Developer ITS/Shared Application Services Stanford University GnuPG Public Key: http://www.stanford.edu/~quanah/pgp.html
openldap-software@openldap.org