=over =item alarm SECONDS X X X =item alarm Arranges to have a SIGALRM delivered to this process after the specified number of wallclock seconds has elapsed. If SECONDS is not specified, the value stored in L|perlvar/$_> is used. (On some machines, unfortunately, the elapsed time may be up to one second less or more than you specified because of how seconds are counted, and process scheduling may delay the delivery of the signal even further.) Only one timer may be counting at once. Each call disables the previous timer, and an argument of C<0> may be supplied to cancel the previous timer without starting a new one. The returned value is the amount of time remaining on the previous timer. For delays of finer granularity than one second, the L module (from CPAN, and starting from Perl 5.8 part of the standard distribution) provides L|Time::HiRes/ualarm ( $useconds [, $interval_useconds ] )>. You may also use Perl's four-argument version of L|/select RBITS,WBITS,EBITS,TIMEOUT> leaving the first three arguments undefined, or you might be able to use the L|/syscall NUMBER, LIST> interface to access L if your system supports it. See L for details. It is usually a mistake to intermix L|/alarm SECONDS> and L|/sleep EXPR> calls, because L|/sleep EXPR> may be internally implemented on your system with L|/alarm SECONDS>. If you want to use L|/alarm SECONDS> to time out a system call you need to use an L|/eval EXPR>/L|/die LIST> pair. You can't rely on the alarm causing the system call to fail with L|perlvar/$!> set to C because Perl sets up signal handlers to restart system calls on some systems. Using L|/eval EXPR>/L|/die LIST> always works, modulo the caveats given in L. eval { local $SIG{ALRM} = sub { die "alarm\n" }; # NB: \n required alarm $timeout; my $nread = sysread $socket, $buffer, $size; alarm 0; }; if ($@) { die unless $@ eq "alarm\n"; # propagate unexpected errors # timed out } else { # didn't } For more information see L. Portability issues: L. =back