13 Oct
2004
13 Oct
'04
10:25 a.m.
Hi,
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? Because this implies that SmallWiki cannot be
deployed on a "productive server" where lots of people log on and do
stuff. Please let me know, I'm grinding my teeth here with the local
sysadmins and I'm losing my patience..
Uff
A desperate "SmallWiki supporting" Michele
13 Oct
13 Oct
11:36 a.m.
Hi Michele,
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
--
Lukas Renggli
http://www.lukas-renggli.ch
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
3:03 p.m.
What bugs were encountered when attempting to run
headless? Is there any
trace output that can be shared?
As Lukas pointed out, I encounter a bug when trying to save programmatically an headless
image. It cannot be restarted.
It was with an old VW 7. Perhaps it has changed since.
Cheers,
Alexandre
-Charles
On Wed, 13 Oct 2004 11:36:50 +0200, Lukas Renggli <renggli(a)iam.unibe.ch>
wrote:
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.iam.unibe.ch/~bergel
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
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
4:26 p.m.
Did you not get an error.log i.e. if you use RuntimePackager for stripping
an error.log file would typically be created. Also just curious what
output you get when you attempt to start the image. Again, as far as
running a SmallWiki I think that running headful is probably ideal. As far
as the re-starting issue, I doubt if it is an issue with VW since saving
images has been around since the beginning of time.
-Charles
On Wed, 13 Oct 2004 15:03:17 +0200, Alexandre Bergel <bergel(a)iam.unibe.ch>
wrote:
--
Using Opera's revolutionary e-mail client: http://www.opera.com/m2/
What bugs were
encountered when attempting to run headless? Is there any
trace output that can be shared?
As Lukas pointed out, I encounter a bug when trying to save
programmatically an headless image. It cannot be restarted.
It was with an old VW 7. Perhaps it has changed since.
Cheers,
Alexandre
-Charles
On Wed, 13 Oct 2004 11:36:50 +0200, Lukas Renggli <renggli(a)iam.unibe.ch>
wrote:
server
Hi Michele,
>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 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
--
Using Opera's revolutionary e-mail client: http://www.opera.com/m2/
3:32 p.m.
Unfortunately I haven't work on that for a long while. I did not keep any log file...
Alexandre
On Wed, Oct 13, 2004 at 09:26:03AM -0500, Charles A. Monteiro wrote:
Did you not get an error.log i.e. if you use
RuntimePackager for stripping
an error.log file would typically be created. Also just curious what
output you get when you attempt to start the image. Again, as far as
running a SmallWiki I think that running headful is probably ideal. As far
as the re-starting issue, I doubt if it is an issue with VW since saving
images has been around since the beginning of time.
-Charles
On Wed, 13 Oct 2004 15:03:17 +0200, Alexandre Bergel <bergel(a)iam.unibe.ch>
wrote:
--
Using Opera's revolutionary e-mail client: http://www.opera.com/m2/
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.iam.unibe.ch/~bergel
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
What bugs
were encountered when attempting to run headless? Is there any
trace output that can be shared?
As Lukas pointed out, I encounter a bug when trying to save
programmatically an headless image. It cannot be restarted.
It was with an old VW 7. Perhaps it has changed since.
Cheers,
Alexandre
-Charles
On Wed, 13 Oct 2004 11:36:50 +0200, Lukas Renggli <renggli(a)iam.unibe.ch>
wrote:
Hi Michele,
>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
--
Using Opera's revolutionary e-mail client: http://www.opera.com/m2/
7383
days inactive
7383
days old
5 comments
4 participants
participants (4)
-
Alexandre Bergel -
Charles A. Monteiro -
Lukas Renggli -
Michele Lanza