Re: [Pharo-users] OSProcess lock image

2017-12-12 Thread Andreas Brodbeck
Am 15.10.16 um 20:00 schrieb Paul DeBruicker: > I have no idea why it happens but sometimes OSProcess resumes working after > doing a > > OSProcessAccessor initialize. > > in a workspace. > > > Hope this helps It did help *me*, thanks for sharing this on the list. I just had the same iss

Re: [Pharo-users] OSProcess lock image

2016-10-20 Thread David T. Lewis
On Wed, Oct 19, 2016 at 10:03:15PM +0200, Hilaire wrote: > Hi Paul, > > Thanks for the tips. > My image was running for days with the computer going to sleep > regularly. Restarting the image solved the problem. That is interesting and helpful, thanks. The process that receives notification of ch

Re: [Pharo-users] OSProcess lock image

2016-10-19 Thread Hilaire
Hi Paul, Thanks for the tips. My image was running for days with the computer going to sleep regularly. Restarting the image solved the problem. Hilaire Le 15/10/2016 à 20:00, Paul DeBruicker a écrit : > I have no idea why it happens but sometimes OSProcess resumes working after > doing a > >

Re: [Pharo-users] OSProcess lock image

2016-10-15 Thread Paul DeBruicker
I have no idea why it happens but sometimes OSProcess resumes working after doing a OSProcessAccessor initialize. in a workspace. Hope this helps HilaireFernandes wrote > Hello, > > On Pharo4, when I type the command: > > OSProcess waitForCommand: 'ls' > > it locks the image,

[Pharo-users] OSProcess lock image

2016-10-15 Thread Hilaire
Hello, On Pharo4, when I type the command: OSProcess waitForCommand: 'ls' it locks the image, I can get back control with [Alt]-. With the same image and VM, this command was previously working, even called from a Seaside component. Any idea? Thanks Hilaire -- Dr. Geo http://drgeo.