Re: [foxboro] VNC - VPN Setup was IP routing/mapping

Hi Jeremy
 
I have no problem taking this back to the list.  
 
My Linux skills are limited, therefore I would appreciate it if you
would send me your scripts.
 
What was not clear to me with VNC was the "windows" vs "unix" behavior.
 - Your explanation below has cleared that up.
 
I have checked and IceWM is available for Novell Suse Linux 10 
(our company preferred distro. - I should be able to get help!!!)
All I need now is to find an old PC.
 
I will keep you posted.
 
Regards
 
Ashley


>>> Jeremy Milum <jmilum@xxxxxxxxx> 00:20:10 24/11/05 >>>
On 11/17/05, Ashley Davey < Ashley.Davey@xxxxxxxxxxxx > wrote:
> I am curious to know how you have set the Linux box, AW and the
VNCserver.
> I like the cost savings achieved by using Linux and VNC.

I would like to keep the discussion on-list, but feel free to contact
me privately if you need.

I have the Linux act as the X-Windows gateway to an AW that has extra
DM's available. The first step is to make sure that you can get an
X-Windows session on the Linux box to start a DM from the AW for a
specific user. I do this with a .xsession script on the Linux box that
uses rexec to run a script on the AW to send the DM to the Linux box.
Test this by logging in locally on the Linux box and see if the DM
starts. I have script already written for both the Linux box and AW
that I know work if you want them. I use a light-weight window manager
that is locked down tight called IceWM. Any window manager would work
as long as you can secure it (Gnome or KDE), but light-weight is
better (NOT Gnome or KDE). I also have XDM set to be the login
manager. I then installed the VNC server. 
 
On Linux the VNC sever acts differently that on Windows. 
Instead of taking over the local display, it actually spawns an
X-Windows session. 
 
So with the VNC server
installed and configured to run from xinetd, you can login as the
above configured user via a VNC client to startup the remote DM. It
sounds complicated, but is pretty easy when taken in steps.

I have the autologoff program from the Cassandra site setup to
shuttoff the DM after 30 min of no activity and the VNC server setup
to shutdown the VNC session after 45 min of no activity. That way the
DM is shutdown cleanly (leaving no open lists) and no stale
connections are left up. This helps greatly with users who open up a
session, but then never close it.

I also use xtrap to record each session to disk for security and
troubleshooting. This allows any session to be replayed at a later
date. I log each start and stop on both the AW and the Linux box.

Anyone have any questions?

--
Patron saints in general are broadband connections to the Almighty
- Michelle Delio, Wired News



 
 
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html
 
foxboro mailing list:             http://www.freelists.org/list/foxboro
to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave

Other related posts: