On Thu, 2016-12-01 at 14:01 +0100, Jack wrote:
> OK, i see now.
>
> For me, the best option is to do a bash script "myscript.bash" :
>
> while read line
> do
> echo "$line"
> done < <(ping netpd.org & echo $!)
>
>
> Then with pd :
>
> [bash myscript.bash(
> >
> >
> [shell]
>
> You
OK, i see now.
For me, the best option is to do a bash script "myscript.bash" :
while read line
do
echo "$line"
done < <(ping netpd.org & echo $!)
Then with pd :
[bash myscript.bash(
|
[shell]
You should be able to terminate the process with the pid return by echo $!
++
Jack
Le
On Thu, 2016-12-01 at 11:29 +0100, Peter P. wrote:
> * Roman Haefeli [2016-12-01 10:52]:
> >
> > Hey all
> >
> > I would like to use Pd to start and stop several instances of a
> > certain
> > command. I need to catch the stdout of the commands in Pd, so I can
> > monitor
On Thu, 2016-12-01 at 11:37 +0100, Jack wrote:
> Le 01/12/2016 à 11:30, Roman Haefeli a écrit :
> >
> > On Thu, 2016-12-01 at 11:09 +0100, Jack wrote:
> > >
> > > Hello Roman,
> > >
> > > Did you try :
> > >
> > > [command & echo $!(
> > > >
> > > >
> > > >
> > > [shell]
> > >
> > > It
Le 01/12/2016 à 11:30, Roman Haefeli a écrit :
> On Thu, 2016-12-01 at 11:09 +0100, Jack wrote:
>> Hello Roman,
>>
>> Did you try :
>>
>> [command & echo $!(
>>>
>>>
>> [shell]
>>
>> It will return the pid of 'command'.
>
> Yes, you're right: It's not even necessary to put that into an extra
>
On Thu, 2016-12-01 at 11:09 +0100, Jack wrote:
> Hello Roman,
>
> Did you try :
>
> [command & echo $!(
> >
> >
> [shell]
>
> It will return the pid of 'command'.
Yes, you're right: It's not even necessary to put that into an extra
script (I thought I had to because of the dollar sign).
* Roman Haefeli [2016-12-01 10:52]:
> Hey all
>
> I would like to use Pd to start and stop several instances of a certain
> command. I need to catch the stdout of the commands in Pd, so I can
> monitor their status. Also, I want to be able to kill them
> individually.
>
> I