Nicolas François wrote:
My opinion is that there is a SIGPIPE which is not catched at one of these
levels: libnss-ldap, libc, or perl.
This could be related to the bug 190072 (libnss-ldap: Processes may
receive SIGPIPE from LDAP session timeouts), but this bug was present in
Sarge.
Also, it could be interresting to test with the previous versions of
libnss-ldap to see when the problem appeared, or with the patch attached
to 190072.
I have no LDAP box, so I can't test. I would appreciate if you could.
You can test with the single perl command sent in the previous messages to
this bug.
I've done some further testing. As with the other reports many dpkg
related items fail, but this appears to be due to libnss-ldap:
[EMAIL PROTECTED]:~$ dpkg-architecture
DEB_BUILD_ARCH=
DEB_BUILD_ARCH_OS=linux
DEB_BUILD_ARCH_CPU=
DEB_BUILD_GNU_CPU=
DEB_BUILD_GNU_SYSTEM=
DEB_BUILD_GNU_TYPE=
DEB_HOST_ARCH=
DEB_HOST_ARCH_OS=linux
DEB_HOST_ARCH_CPU=
DEB_HOST_GNU_CPU=
DEB_HOST_GNU_SYSTEM=
DEB_HOST_GNU_TYPE=
[EMAIL PROTECTED]:~$ dpkg --print-architecture
i386
[EMAIL PROTECTED]:~$ ${CC:-gcc} -dumpmachine
i486-linux-gnu
[EMAIL PROTECTED]:~/tmp/src/vino-2.13.5$ perl -e '@foo=getpwnam
($ENV{'LOGNAME'});
> open(STDIN,"< debian/changelog") || die "error1";
> open(P,"tail -n 40 |") || die "error2";
> print "status1: $?\n";
> close(P); print "status2: $?\n"'
status1: 0
status2: 13
By simply downgrading libnss-ldap to 238-1 (sarge's version) they once
again work fine as a normal user:
[EMAIL PROTECTED]:~$ dpkg-architecture
DEB_BUILD_ARCH=i386
DEB_BUILD_ARCH_OS=linux
DEB_BUILD_ARCH_CPU=i386
DEB_BUILD_GNU_CPU=i486
DEB_BUILD_GNU_SYSTEM=linux-gnu
DEB_BUILD_GNU_TYPE=i486-linux-gnu
DEB_HOST_ARCH=i386
DEB_HOST_ARCH_OS=linux
DEB_HOST_ARCH_CPU=i386
DEB_HOST_GNU_CPU=i486
DEB_HOST_GNU_SYSTEM=linux-gnu
DEB_HOST_GNU_TYPE=i486-linux-gnu
I tested a few more versions of the libnss-ldap package:
238-1.1 - worked
238-1.2 - worked
251-1 - broken
So, it seems the problem was introduced between 238-1.2 and 251-1.
--
Jamin W. Collins
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
