Hello,
Thanks to Simone's answers on jabber, we could identify a possible cause
for this bug.
It seems this issue is related to using getpwnam on an LDAP system.
perl -e 'open(STDIN,"< debian/changelog") || die "error1";
open(P,"tail -n 40 |") || die "error2";
close(P); print "status: $?\n"'
works (i.e. the status is 0).
but perl -e '@foo=getpwnam ($ENV{'LOGNAME'});
open(STDIN,"< debian/changelog") || die "error1";
open(P,"tail -n 40 |") || die "error2";
close(P); print "status: $?\n"'
does not always work (sometimes the status is 13, sometime it is 0; nscd may
help).
This could be reproduced on another LDAP system (other than Simone's one).
Simone, I forgot to ask you if you're using nscd.
Simon, do you also have an LDAP system? Do you use nscd?
What's the output of:
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"'
I don't know whether it is:
* a dpkg bug
* a perl bug
* an LDAP bug
* an LDAP configuration issue
perl and libnss-ldap maintainers, do you have an opinion?
Thanks in advance,
--
Nekral
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
