| delorie.com/archives/browse.cgi | search |
| Mailing-List: | contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm |
| Sender: | cygwin-owner AT sourceware DOT cygnus DOT com |
| Delivered-To: | mailing list cygwin AT sourceware DOT cygnus DOT com |
| Message-ID: | <37166F76.97ECB70C@broad-reach.net> |
| Date: | Thu, 15 Apr 1999 16:00:06 -0700 |
| From: | Greg Mathis <gmathis AT broad-reach DOT net> |
| X-Mailer: | Mozilla 4.5 [en] (WinNT; I) |
| X-Accept-Language: | en |
| MIME-Version: | 1.0 |
| To: | cygwin <cygwin AT sourceware DOT cygnus DOT com> |
| Subject: | perl system("kill") function |
I am having a new problem using a perl script that runs in tcsh or bash.
This script ran fine before I upgraded to NT4.0 Service Pack 4.
I want to search though the list of processes and use 'kill' to send the
USR1 and USR2 POSIX signals to a particular C program built with gcc in
cygwin.
Perl code snippet:
$processList = `ps`;
(find the process id of interest ($pid) by searching by program name
through $processList)
system("kill -USR1 $pid);
After I run the perl program, the "ps" and "kill" from within the perl
script now show up when I call "ps" from the shell.. So if I run this
script over and over, the process list keeps growing. This did not
happen when I had only Service Pack 3 installed.
Any ideas on what is happening?
TIA,
Greg
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com
| webmaster | delorie software privacy |
| Copyright © 2019 by DJ Delorie | Updated Jul 2019 |