in reply to Script Timeouts

Are you using Oracle on Solaris perchance? A quick tour of the web turned up the following in Google's Usenet archive groups.google.com.

This might bite you if you have previously set an alarm and cleared it (but not, as the post points out).

Then again, this thing is so specific (Oracle, Solaris, and you need to have set and cleared an alarm around the connect call), that it's probably not relevant to your problem.

CU
Robartes-

Replies are listed 'Best First'.
Re: Re: Script Timeouts
by Tanalis (Curate) on Nov 08, 2002 at 09:01 UTC
    I'm using Sybase on Solaris .. but it's definitely Perl, not Sybase, that's killing the process.

    I'm wondering if it's something that's been compiled in locally to prevent system resources getting eaten forever on the batch machines, and it's cascaded down onto the workstations too. (if that's the case there's probably nothing I can do about it .. *sigh*)

    --Foxcub

[reply]

In Section Seekers of Perl Wisdom