On Sun, 27 May 2007, Stephen Gran wrote:
> It seems odd, but not impossible.  I'll take another look at nss-pgsql
> and let you know - if I can force it to set errno to ERANGE, and it
> continues to break, then the problem is with updatedb.  If it doesn't
> return ERANGE, then the problem is with the backend.

AFAIK, libnss-pgsql sets errno appropriately:

Line 442 of src/backend.c has this:
 BAIL_OUT:
        /* Set errnop so glibc will call the us again with a bigger buffer */
        if (status == NSS_STATUS_TRYAGAIN)
                *errnop = ERANGE;

Cheers,
-- 
Raphaël Hertzog

Premier livre français sur Debian GNU/Linux :
http://www.ouaza.com/livre/admin-debian/

Reply via email to