in reply to Scheduling internal functions/processes to run within a program (like cron does programs)

Rather than the sleep, you could use the asynchronous method :
alarm and a signal handler
(can be combined with fork)
$SIG{ALRM} = sub { #Your code here }; eval { alarm(60); # Your code will be executed in 60 seconds # do something here # anytime during this 60 sec you can cancel the alarm with alarm(0 +) };
Example of use:
You can manage timeout by limiting the time allowed to answer
(and/or even pop up a message to say "$x sec remaining...")

UPDATE :
As my previous example seems to be unclear, here is a complete example from a previous post to manage the timeout :
#!/usr/local/bin/perl -w use strict; use IO::Socket; { my $timeout = 0; my $sock = undef; $SIG{ALRM} = sub {$timeout = 1; die}; eval { alarm (2); $sock = new IO::Socket::INET(PeerAddr=> '10.1.1.18',PeerPort => + 29,); alarm (0); } die "Can't open socket: timeout=$timeout\n" if ($timeout or !$sock); print "I would print to the socket now, if I knew what I was connecte +d to\n"; close ($sock); }


"Only Bad Coders Badly Code In Perl" (OBC2IP)
  • Comment on Re: Scheduling internal functions/processes to run within a program (like cron does programs)
  • Select or Download Code

Replies are listed 'Best First'.
(tye)Re: Scheduling internal functions/processes to run within a program (like cron does programs)
by tye (Sage) on May 24, 2001 at 02:03 UTC

    Until "safe Perl signal handlers" gets rolled out in a future version of Perl, I'd avoid this type of solution as each instance of a Perl signal handler running introduces a small but non-zero chance that Perl will corrupt some of its internal structures, eventually leading the script misbehaving.

            - tye (but my friends call me "Tye")
Re: Re: Scheduling internal functions/processes to run within a program (like cron does programs)
by larryk (Friar) on May 23, 2001 at 16:46 UTC
    two words arhuman - "split infinitive" :-D
      "Personally, I like to defiantly split my infinitives. :-) "
      -- Larry Wall

      Found today on Perlarchive ;-)

      But, as I'm not larry =>

      "Only Bad Coders Code Badly In Perl" (OBC2BIP)
        touché!