* Philippe M. Chiasson ([EMAIL PROTECTED]) [021003 23:42]: > crypt() is not required to be re-entrant, and is usually not re-entrant > or thread-safe. But, some platforms provide a crypt_r() function, a > re-entrant version of crypt.
We looked into this some more and our Perl believes it is using crypt_r. There is, evidently, a problem with Linux's glibc-2.2.5 implementation of crypt(): http://marc.theaimsgroup.com/?l=perl5-porters&m=103012185631309&w=2 For the time being we can work-around until we move to a Perl (or a glibc) which doesn't expose this issue. Rick -- http://www.rickbradley.com MUPRN: 374 (59F/57F) | drunken ass is just random email haiku | spilling out everything I | can think of. Enjoy. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
