in reply to $SIG{'ALRM'} on FreeBSD

Seems to work fine:
perl -e '$SIG{ALRM} = sub { die "signal alarm caught!\n" }; kill 14, $ +0'

STDERR: signal alarm caught!

`uname -a`: FreeBSD zuluz 6.0-RELEASE FreeBSD 6.0-RELEASE #0: Thu Nov  3 09:36:13 UTC 2005     root@x64.samsco.home:/usr/obj/usr/src/sys/GENERIC  i386


Replies are listed 'Best First'.
Re^2: $SIG{'ALRM'} on FreeBSD
by b888 (Beadle) on Feb 24, 2006 at 12:03 UTC

    Yes, that works for me to :) The most strange thing is that it falls under some conditions. Sometimes beyond 1 or 2 days, sometimes in a week of work it falls. And that is what i'm trying to understand. Why?

    p.s. Average load is 10-30 request per second.

      Average load is 10-30 request per second.

      If I had that kind of load, I think I'd be tempted to use Net::Server::Prefork. Call me crazy.

        Thanks for tip, but that will not help in my case :) In fact i use 1-thread 1-request server. No concurent requests. Next request is not served untill current one finished. It's limited by buisness logic.