I have a couple long running perl scripts in windows (strawberry perl) that I'm working on.

1. The first process is a parent monitoring process. It restarts the child process every 24 hours and will be always running.
2. The second is the child payment processing script. It is imperative that this process completes whatever it's doing before being shutdown.

It's my understanding that signal handling [doesn't work](http://perldoc.perl.org/perlport.html#System-Interaction) in perl on win32 and that it shouldn't be relied on. Is there some other way that I can handle a signal? `Win32::Process::Kill` seems to kill the process without letting it safely shut down.

This is the signal handling that I've tried...

```
#Child
my $interrupted = 0;
$SIG{INT} = sub{$interrupted = 1;};
while(!$interrupted){
  #keep doing your thing, man
}

#Parent
my $pid = open2(\*CHLD_OUT,\*CHLD_IN,'C:\\strawberry\\perl\\bin\\perl.exe','process.pl');
kill INT=>$pid;
waitpid($pid,0);

```

The only other thing I can think of is to open a socket between the two processes and write messages across the socket. But there must be something easier. Anyone know of any module that can do this?

**Update**

I've started working on creating a "*signal*" mechanism via `IO::Socket::INET` and `IO::Select` by [opening a socket](https://gist.github.com/gordolio/9371193). This appears to work and I'm thinking of writing a module that is compatible with [AnyEvent](https://metacpan.org/pod/AnyEvent#SYNOPSIS). But I'm still interested in an implementation that doesn't require opening a listening port and that doesn't require a server/client relationship. Is it possible to do this by subscribing to and firing custom events in windows?