On Mon, Aug 12, 2002 at 05:53:04PM -0500, David M. Lloyd wrote:
> On Mon, 12 Aug 2002, Joe Slagel wrote:
>
> > Hi All,
> >
> > We're seeing some very odd behavior with using alarm() around the
> > DBI->connect() call only on Solaris platforms. It appears that even
> > though we clear the alarm after a successful connection, for some reason
> > the alarm signal is still getting sent and we receive a very nice "Alarm
> > Clock" message. The following script demostrates the problem (on
> > Solaris), but works fine on Linux. Anyone have any guesses why this may
> > be?
>
> This is a Perl bug on Solaris. Doing an alarm(0) doesn't really clear the alarm.
Can you point me to a url for more information on the bug?
Tim.
> You might try alarm(big number here) but I'm not sure that will
> work either. What I do is do $SIG{ALRM} = 'IGNORE' when I'm not using it.
> It still leaves a small race condition, but that's all I can do.
>
> - D
>
> <[EMAIL PROTECTED]>
>
