2017-12-29 16:53 GMT+01:00 Denis Kudriashov <dionisiydk@gmail.com>:

2017-12-29 16:13 GMT+01:00 Andrei Stebakov <lispercat@gmail.com>:

...

Nicolai, the maximize/non-maximize trick worked! Thanks! I wonder if it's an easy fix to put in Pharo.

So it means that something in image is not initialised. It can be another bug of wrong startup order

Maybe a problem on the image and the vm side. Even in headless mode, starting pharo creates a window. Even if it is hidden, it has some size. Quit and Saving an image will write the current width/height into the image file. Starting the vm will create a window and set the size of the window to the last size. The window is always created in normal (not-maximized) mode and the available size is a little bit smaller than for a maximized window. Now, the image checks for a change of the size of the current DisplayScreen instance and the actual screen size. If this is different (as in this case) a new DisplayScreen is initialized which will call a full screen update (ioForceDisplayUpdate). And this method will show a hidden (headless) image.

...

On Fri, Dec 29, 2017 at 6:22 AM, phil@highoctane.be <phil@highoctane.be> wrote:

...

I am using nssm because the service option is broken.

The code seems to still be in the image but disabled (there are quite a few things like that actually).

Phil

On Fri, Dec 29, 2017 at 11:59 AM, Torsten Bergmann <astares@gmx.de> wrote:

...

Hi, (cross posting vm-dev)

nssm is nice - but requires additional tools.

Since the days of Squeak the windows VM had the

-service "ServiceName"

option and one was able to run Squeak as a windows service out of the box.

See http://wiki.squeak.org/squeak/105 for details.

This option allows to register/deregister with the windows service manager and run a headless image.

I run a Squeak Wiki (Swiki/Comanche) since years with this and it is very nice and stable.

Unfortunately this is broken in recent Pharo VMs and so far Esteban or others did not have the time to look into this issue. Would be really nice if this option could be recovered in 2018. So one could easily deploy and run Seaside or Teapot/Tealight or Zinc/WebClient based web services on Windows.

If we want to deploy Smalltalk based web applications or services on Windows we should support that. It will keep Windows administrators happy and we would integrate with the whole ecosystem (for instance you can start/stop a service using Windows scripting for doing backups, etc.) right out of the box.

Bye T.

Gesendet: Freitag, 29. Dezember 2017 um 11:36 Uhr Von: "phil@highoctane.be" <phil@highoctane.be> An: "Any question about pharo is welcome" <pharo-users@lists.pharo.org> Betreff: Re: [Pharo-users] Running headless on Windows

If you want to run Pharo as a service, I have found nssm to be working well. https://nssm.cc

Phil

On Dec 29, 2017 09:25, "Nicolai Hess" <nicolaihess@gmail.com[mailto: nicolaihess@gmail.com]> wrote:

2017-12-29 3:07 GMT+01:00 Andrei Stebakov <lispercat@gmail.com[mailto: lispercat@gmail.com]>: Pierce, I tried all of those "no display" options, the result is the same

On Dec 28, 2017 8:37 PM, "Pierce Ng" <pierce@samadhiweb.com[mailto: pierce@samadhiweb.com]> wrote:On Wed, Dec 27, 2017 at 04:58:39PM +0100, Cyril Ferlicot D. wrote:

...

On 12/27/2017 04:39 PM, Andrei Stebakov wrote:

...

When I run Pharo 6.1 with -- headless option on Windows, it executes the eval command as expected but during the execution (which lasts 4 sec) it opens the Pharo GUI. Is it expected? I thought headless means that the whole execution would happen in the background

I think that currently Pharo does not have a "real" headless. But I heard there was work on that part for Pharo 7.

I know OP is talking about Windows... I've been running server applications on Linux without X11 with -vm-display-null and in-image RFBServer for access to Pharo over VNC. This works very well for me.

I believe "real" headless means GUI is not run at all and therefore does not consume CPU cycles, which is very welcome. Meanwhile, maybe -vm-display-null works on Windows for scripting purposes?

Pierce

Hi Andrei,

can you try this:

Open Pharo normal (no headless option). Change the window size to "not-maximized" (eve if it is actually not maximized, maximize it ones and change it back to "not-maximized") Save and quit the image.

After that, a call like

pharo --headless pharo.image eval "DateAndTime now" will write the output to the stdout file, without opening a window.