Hi!
I have increased the size of the memory of the VM (by modifying the plist option). But apparently, there is not enough memory to run the process watcher? Any idea why? Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
What do you mean exactly? Doru On Mon, May 12, 2014 at 12:45 AM, Alexandre Bergel <[hidden email]> wrote: Hi! "Every thing has its own flow"
_______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
I have increased the size of the VM, by fiddling in the plist. But apparently, the process watcher could not lunch properly. I think it has an impact on using cmd - . to interrupt the current process.
Am i the only one to experience this? Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. On May 13, 2014, at 5:34 PM, Tudor Girba <[hidden email]> wrote: > What do you mean exactly? > > Doru > > > On Mon, May 12, 2014 at 12:45 AM, Alexandre Bergel <[hidden email]> wrote: > Hi! > > I have increased the size of the memory of the VM (by modifying the plist option). But apparently, there is not enough memory to run the process watcher? Any idea why? > > Alexandre > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > _______________________________________________ > Moose-dev mailing list > [hidden email] > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > > > -- > www.tudorgirba.com > > "Every thing has its own flow" > _______________________________________________ > Moose-dev mailing list > [hidden email] > https://www.iam.unibe.ch/mailman/listinfo/moose-dev _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
How are you starting the watcher? Are you referring to the CPU Watcher? Doru On Wed, May 14, 2014 at 12:09 AM, Alexandre Bergel <[hidden email]> wrote: I have increased the size of the VM, by fiddling in the plist. But apparently, the process watcher could not lunch properly. I think it has an impact on using cmd - . to interrupt the current process. "Every thing has its own flow"
_______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
On Wed, May 14, 2014 at 8:20 AM, Tudor Girba <[hidden email]> wrote:
I think Alex is referring to the notification that we get in Pharo when we increase vm heap size in plist file/settings. This is a notification that appears on image launch and indicates the message Alex is referring to. I recently increase my heap size to 1.3 GB (I could not go beyond because then vm launch failed). When I started my image with the VM, I got the watcher notification. I am not sure if we have any side-effects because once notification closed, I could use the image with the vm without any problems.
regards, Usman
_______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
Free forum by Nabble | Edit this page |