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

Re: ldap tool result codes

To: ando@sys-net.it
Subject: Re: ldap tool result codes
From: Howard Chu <hyc@symas.com>
Date: Wed, 05 Oct 2005 06:23:55 -0700
Cc: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>, OpenLDAP Commit <openldap-commit2devel@OpenLDAP.org>
In-reply-to: <35737.131.175.154.56.1128500834.squirrel@131.175.154.56>
References: <200510042322.j94NMRZf039495@cantor.openldap.org> <hbf.20051005b0ev@bombur.uio.no> <35737.131.175.154.56.1128500834.squirrel@131.175.154.56>
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20050925 SeaMonkey/1.1a

Pierangelo Masarati wrote:

Maybe we should change all the LDAP tools to always return some LDAP error code, and some special code when it cannot or when an LDAP code does not make sense?
The point is: LDAP error codes are integers, while command return codes for portability __should__ limited to "chars" (o->255) as far as I can tell (please correct me). I'd prefer LDAP error codes, too (at least the most "popular" ones, which are well below 255).

Right. 0-255 for exit status.

--
 -- Howard Chu
 Chief Architect, Symas Corp.  http://www.symas.com
 Director, Highland Sun        http://highlandsun.com/hyc
 OpenLDAP Core Team            http://www.openldap.org/project/

References:
- ldap tool result codes (was: commit: ldap/tests/scripts test007-replication test018-syncreplication-persist)
  - From: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>
- Re: ldap tool result codes (was: commit: ldap/tests/scripts test007-replication test018-syncreplication-persist)
  - From: "Pierangelo Masarati" <ando@sys-net.it>

Prev by Date: Re: ldap tool result codes
Next by Date: Re: commit: ldap/include ldap.h
Index(es):
- Chronological
- Thread