Re: [Pharo-dev] Services and -vm-display-null

Jan. 23, 2014

      wellâ¦ you can always modify BasicCommandLineHandler to respond as you want:

BasicCommandLineHandler>>handleArgument: aString

	"give priority to subcommands"
	self handleSubcommand == self
		ifFalse: [ ^ self ].

	"check for default options"
	aString ifEmpty: [ ^ self default ].

	aString = '--version'
		ifTrue: [ ^ self version ].

	aString = '--help'
		ifTrue: [ ^ self help ].

	aString = '--list'
		ifTrue: [ ^ self list ].

	aString = '--copyright'
		ifTrue: [ ^ self copyright ].

	aString = '--no-quit'
		ifTrue: [ ^ self noQuit ].

	"none of the previous options matched hence we output an error message"
	self error.

you can just remove the last line (âself error"). Is a hackâ¦ but Iâm kinda sure it will work :)

Esteban

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
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/

Re: [Pharo-dev] Services and -vm-display-null

Esteban Lorenzano