Smalltalk › Pharo › Pharo Smalltalk Users

Using the new OSProcess still no Stdout string

‹ Previous Topic Next Topic ›
 
classic Classic list List threaded Threaded
♦
♦
 6 messages Options
kilon.alios
Reply | Threaded
Open this post in threaded view
♦
♦
|

Using the new OSProcess still no Stdout string

kilon.alios
Still experience the same problem, is this suppose to be fixed with new OSProcess ?


John Pfersich
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: Using the new OSProcess still no Stdout string

John Pfersich
You want to use waitForCommand: instead of command:, like

Transcript show: (PipeableOSProcess waitForCommand: 'whoami') output

command: doesn't wait for output and is useful only for commands that don't return anything. It's kind of useless for anything that returns values. I haven't tried this on Pharo 5, I've gotten it to work on Pharo 4. 



On Friday, March 4, 2016, Dimitris Chloupis <[hidden email]> wrote:
Still experience the same problem, is this suppose to be fixed with new OSProcess ?


John Pfersich
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: Using the new OSProcess still no Stdout string

John Pfersich
I just loaded the latest image and vm using

curl get.pharo.org/alpha+vmLatest | bash


and OSProcess and CommandShell seem to work OK. 





On Friday, March 4, 2016, john pfersich <[hidden email]> wrote:
You want to use waitForCommand: instead of command:, like

Transcript show: (PipeableOSProcess waitForCommand: 'whoami') output

command: doesn't wait for output and is useful only for commands that don't return anything. It's kind of useless for anything that returns values. I haven't tried this on Pharo 5, I've gotten it to work on Pharo 4. 



On Friday, March 4, 2016, Dimitris Chloupis <<a href="javascript:_e(%7B%7D,&#39;cvml&#39;,&#39;kilon.alios@gmail.com&#39;);" target="_blank">kilon.alios@...> wrote:
Still experience the same problem, is this suppose to be fixed with new OSProcess ?


John Pfersich
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: Using the new OSProcess still no Stdout string

John Pfersich
In reply to this post by John Pfersich
Well, I have to take back the comment on command:. I have this code snippet that gets output from a command:

| p d  |
p := (PipeableOSProcess command: 'netstat -a | grep LISTEN | grep  27017').
p keepInitialStdOutOpen: true.
d := Delay forMilliseconds: 500.
d wait.
[Transcript show: (p next: 300); flush. p isComplete] whileFalse: [d wait].
Transcript show: 'Error output';
cr;
show: (p errorUpToEnd).
p closeOutput.

The netstat takes forever on a Mac, which is why the delays are so long. The 

On Friday, March 4, 2016, john pfersich <[hidden email]> wrote:
You want to use waitForCommand: instead of command:, like

Transcript show: (PipeableOSProcess waitForCommand: 'whoami') output

command: doesn't wait for output and is useful only for commands that don't return anything. It's kind of useless for anything that returns values. I haven't tried this on Pharo 5, I've gotten it to work on Pharo 4. 



On Friday, March 4, 2016, Dimitris Chloupis <<a href="javascript:_e(%7B%7D,&#39;cvml&#39;,&#39;kilon.alios@gmail.com&#39;);" target="_blank">kilon.alios@...> wrote:
Still experience the same problem, is this suppose to be fixed with new OSProcess ?


kilon.alios
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: Using the new OSProcess still no Stdout string

kilon.alios
thanks for freezing my image !!! Argggg !!!! :D

On Sat, Mar 5, 2016 at 10:44 AM john pfersich <[hidden email]> wrote:
Well, I have to take back the comment on command:. I have this code snippet that gets output from a command:

| p d  |
p := (PipeableOSProcess command: 'netstat -a | grep LISTEN | grep  27017').
p keepInitialStdOutOpen: true.
d := Delay forMilliseconds: 500.
d wait.
[Transcript show: (p next: 300); flush. p isComplete] whileFalse: [d wait].
Transcript show: 'Error output';
cr;
show: (p errorUpToEnd).
p closeOutput.

The netstat takes forever on a Mac, which is why the delays are so long. The 

On Friday, March 4, 2016, john pfersich <[hidden email]> wrote:
You want to use waitForCommand: instead of command:, like

Transcript show: (PipeableOSProcess waitForCommand: 'whoami') output

command: doesn't wait for output and is useful only for commands that don't return anything. It's kind of useless for anything that returns values. I haven't tried this on Pharo 5, I've gotten it to work on Pharo 4. 



On Friday, March 4, 2016, Dimitris Chloupis <[hidden email]> wrote:
Still experience the same problem, is this suppose to be fixed with new OSProcess ?


Pierce Ng-3
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: Using the new OSProcess still no Stdout string

Pierce Ng-3
On Sat, Mar 05, 2016 at 02:19:10PM +0000, Dimitris Chloupis wrote:
> thanks for freezing my image !!! Argggg !!!! :D
>
> On Sat, Mar 5, 2016 at 10:44 AM john pfersich <[hidden email]> wrote:
> > p := (PipeableOSProcess command: 'netstat -a | grep LISTEN | grep  27017').

netstat -an

Option n avoids DNS lookup which is the likely cause of the delay.

Pierce

Free forum by Nabble Edit this page