signal processing INT or TERM

by **rsarpi** » Fri, 31 Oct 2008 05:50:54 GMT

perl 5.8.2
OS: AIX fully POSIX compliant

my script moves files from one dir to another.
When I want my script to stop, should I pass it along the signal INT
or TERM?

INT just interrupts the script.  It finishes whatever it's processing
and then it's done.

TERM on the other hand, just sends a TERMination signal, waits a few
seconds, then KILLs the program.  TERM is more common I guess when
starting/stopping unix shell scripts in the init dir.

My fear is that if I pass the TERM signal, maybe the system will chop
off the files that are being moved on the fly.  The "few seconds" are
unpredictable in value at least on my system. So the system might say
'it's been too long, let's kill it."

Any thoughts? Is there a "perlish" way to do it?

by **pangj** » Fri, 31 Oct 2008 23:20:37 GMT



 > Message du 30/10/08 10:45



SIGTERM and SIGINT are almost the same usage. See 'man 8 kill' and look for signals.
You may want to redefine the POSIX signal handlers.
See also L. Stein's "Network programming with Perl", that will give the full details.


Jeff.
 http://www.**--****.com/ 

 Crez votre adresse lectronique  XXXX@XXXXX.COM  
 1 Go d'espace de stockage, anti-spam et anti-virus intgrs.

by **carnildo** » Sun, 02 Nov 2008 05:22:20 GMT



I'd send a custom signal (say, USR1).  When the script receives that
signal, it sets a flag indicating it should perform a clean exit.
Totally untested:

----------
my $done = 0;

sub sigusr {
    $done = 1;
}

$SIG{USR1} = \&sigusr;

while(!$done)
{
    # Do something
}
# Clean up and exit
----------

It won't work if "do something" is perpetually blocked on a read or
somesuch, but if you wake up periodically to go through the loop,
you'll be fine.

-- 
Mark Wagner

signal processing INT or TERM

signal processing INT or TERM

Jump to:

Next

signal processing INT or TERM

Re:signal processing INT or TERM

Re: signal processing INT or TERM

Similar Threads:

Who is online