If you call getpwuid(something); in perl while >=sys-auth/nss_ldap-240 is active, all further calls to system(); qx(); open(|pipe_to_executable); won't execute anything. I think it's the same behaviour that affected portage a while ago (cf. bug #147625). Is there any fix for that (except for downgrading nss_ldap). Regards, Torsten Reproducible: Always
(In reply to comment #0) > I think it's the same behaviour that affected portage a while ago (cf. bug > #147625). Is there any fix for that (except for downgrading nss_ldap). If it's the same issue, see Bug 156511.
No, I don't think that it's quite the same. In fact, getpwuid works fine, even if called several times in a loop, only AFTERWARDS every system-execution fails. It's not a hang like described in bug #156511... But as it seems to be somehow connected to the mentioned upstream bug, I guess I'll just continue to use sys-auth/nss_ldap-239-r1 until the end of time. ;o)
(In reply to comment #0) More precisely > If you call > > getpwuid(something); in list context(!) > > in perl while >=sys-auth/nss_ldap-240 is active, all further calls to > system(); > qx(); > open(|pipe_to_executable); > > won't execute anything. At least in my few tests with calling getpwuid or getpwnam in scalar context system() calls still work.
please retest with 257. It contains a SIGPIPE fix.
(In reply to comment #4) I tested 257 in list context @pwflds = getpwuid( $> ); and scalar context $pwflds = getpwuid( $> ); each with one call to system(); qx(); open(|pipe_to_executable); and they all worked.
Thanks, closing.