Hi,
Sorry for the long delay in my response, it took me a while to get back to
this.
when I try the command in msys bash I get
PID PPID COMMAND
5324 1 /msys/bin/bash
5976 5324 /msys/bin/bash
6184 5324 /msys/bin/ps
But when I try in command line, I get
Can't find string terminator "'" anywhere be
Under windows command line:
ps -ef | perl -ane '1..1 and /^(.*)CO?MM?A?N?D/ and $s=length
$1;s/^.{$s}//; print "@F[1,2] $_"'
Can't find string terminator "'" anywhere before EOF at -e line 1.
ps -ef | perl -ane "1..1 and /^(.*)CO?MM?A?N?D/ and $s=length
$1;s/^.{$s}//; print qq{@F[1,2] $_}"
PID PPI
On 15-04-12 07:14 AM, Ole Tange wrote:
You mean in sub Job::kill():
# Wait up to 200 ms between TERMs - but only if any pids
are alive
my $sleep = 1;
for (my $sleepsum = 0; kill 0, $family_pids[0] and $sleepsum < 200;
$sleepsum += $sleep)
On Mon, Apr 13, 2015 at 1:53 AM, Martin d'Anjou
wrote:
> On 15-04-12 07:14 AM, Ole Tange wrote:
>> On Sat, Apr 11, 2015 at 12:56 AM, Martin d'Anjou
>> wrote:
:
>>> Q2:
> In terms of a real life scenario, I can offer an overview of my workflow.
>
> Some processes take a long time to terminate fro
On Mon, Apr 13, 2015 at 3:44 PM, Martin d'Anjou
wrote:
> On 15-04-12 07:14 AM, Ole Tange wrote:
:
> I propose two solutions:
> - Change the code to only kill the parent process (existing users will have
> to change their application code to kill children processes themselves)
> - Do not change the
On 15-04-13 03:31 PM, Ole Tange wrote:
:
The delay between sending SIGTERM and
hearing back from the child-most process can be more than 200ms.
Can I ask you to measure it? If we are talking 1000 ms I will not see
a big problem in changing the 200 ms to 1000 ms.
I have one case where I had to
On 15-04-13 03:46 PM, Ole Tange wrote:
On Mon, Apr 13, 2015 at 3:44 PM, Martin d'Anjou
wrote:
On 15-04-12 07:14 AM, Ole Tange wrote:
:
I propose two solutions:
- Change the code to only kill the parent process (existing users will have
to change their application code to kill children process
