13 Oct
2004
13 Oct
'04
2:59 p.m.
I can confirm that. I am not currently using VNC although I want to check
it out, but instead Exceed. The only way somebody can get in is by knowing
a user and password. Also they can only get in from the inside since the
firewall would block any attempts to hook up to the X session. VisualWorks
has been running in production headless for years. For example, VisualWave
servers at Penn State which run the student info system including
registration. Countless other installations. I believe that the issue is
that X11 libraries need to be around but VisualWorks can run headless and
does not need to run from inside a unix X session. In anycase, I agree
that there are advantqages to running "headfully", I think that there are
many apps that could also benefit from said approach. However, that goes
against the grain with most sysadmins that are used to doing things in
"old ways" that were driven by a different set of constraints.
What bugs were encountered when attempting to run headless? Is there any
trace output that can be shared?
-Charles
On Wed, 13 Oct 2004 11:36:50 +0200, Lukas Renggli <renggli(a)iam.unibe.ch>
wrote:
Hi Michele,
--
Using Opera's revolutionary e-mail client: http://www.opera.com/m2/
I'm trying to use SmallWiki here on a server.
The way I see it, is that
even despite using VNC to keep the X session, it means that right now
on that server there is always a VNC session. So, if somebody else is
connecting with VNC to the server he will see the SmallWiki Visualworks
windows. Is that correct?
you can have as many different VNC (and X11) Sessions on the same server
as you want. You could protect your VNC Session with a password, so that
you are the only one able to access it.
The VisualWorks documentation says, that it is possible to run the VM
headless. Alexander tried to put some scripts together, but we gave up
because of some very strange bugs when running VisualWorks headless.
We are basically running all our Smalltalk server-applications in VNC
Sessions. Think of the advantages: this gives the power to update and
maintain the application without having to shut-down the server.
Cheers,
Lukas