note afoken <p>Strawberry Perl runs on Windows. Windows does not have signals. POSIX systems like Linux have signals.</p> <p>Perl emulates some minor aspects of <c>kill()</c> on Windows, but you can't expect the emulation to be perfect.</p> <p>From [doc://perlport]:</p> <blockquote> <c>kill()</c> doesn't have the semantics of <c>raise()</c>, i.e. it doesn't send a signal to the identified process like it does on Unix platforms. Instead <c>kill($sig, $pid)</c> terminates the process identified by <c>$pid</c>, and makes it exit immediately with exit status <c>$sig</c>. As in Unix, if <c>$sig</c> is 0 and the specified process exists, it returns true without actually terminating it. (Win32) </blockquote> <blockquote> <c>kill(-9, $pid)</c> will terminate the process specified by <c>$pid</c> and recursively all child processes owned by it. This is different from the Unix semantics, where the signal will be delivered to all processes in the same process group as the process specified by <c>$pid</c>. (Win32) </blockquote> <p>From [doc://perlwin32]:</p> <blockquote> Signal handling may not behave as on Unix platforms (where it doesn't exactly "behave", either :). For instance, calling <c>die()</c> or <c>exit()</c> from signal handlers will cause an exception, since most implementations of <c>signal()</c> on Win32 are severely crippled. Thus, signals may work only for simple things like setting a flag variable in the handler. Using signals under this port should currently be considered unsupported. </blockquote> <p>Alexander</p> <div class="pmsig"><div class="pmsig-747201"> --<br> Today I will gladly share my knowledge and experience, for there are no sweeter words than "I told you so". ;-) </div></div> 794938 794938