Tim Bunce wrote: [alarm(0) fails to silence SIGALRM]
>A known problem with how Solaris handles dynamically loading a >library that uses threads into a executable that doesn't. > >A probable workaround is to "use DBD::Oracle;" before the alarm() >call. Yes, that fixes the problem. Do you have more details about the Solaris bug? I wonder whether there is anything Perl could do about it, such as setting a flag when alarm() is called and giving a warning if a library with threads is loaded while an alarm is active. -- Ed Avis <[EMAIL PROTECTED]>
