Thanks Sven bue I have no issues on Pharo 2
The problem is with Pharo 3 on the latest VM
With services and all this I was referring not to things inside the image but in the OS (the headless image as service)
Yes, having a init.d script to start the image is the goal
Are you using your scrips on any Pharo 3?
On Jan 23, 2014, at 1:32 PM, Sven Van Caekenberghe <
sven@stfx.eu> wrote:
Hi,
On 23 Jan 2014, at 16:14, Sebastian Sastre <sebastian@flowingconcept.com> wrote:
Hi there,
What are you using to monitor processes in headless images?
I ask because the new way to start a headless image in linux is:
pharo-vm/pharo -vm-display-null your.image �no-quit
And it seems that it always quits
I always start images with no preconfigured servers/services in them and then use an st script to start servers/services. Then you are using the STCommandLineHandler that does _not_ quit by default.
Furthermore, I have a script to control image/vm start/stop/restart/pid which I use from /etc/init.d with monit using these last scripts.
If you want, I can send you the code.
You could try extracting it from http://stfx.eu/pharo-server/ but that page is old.
HTH,
Sven
For example supervisord* is really unhappy about this way to run a service.
It�s really unfortunate. This is a show stopper.
Is there an OS signal being sent when you use -vm-display-null or the process stays normally up?
There is no way to run a headless image like we used to?
sebastian
o/
*http://supervisord.org/