The reason that I use this suite is to leave a Linux X session running
24/7, then disconnect and reconnect to it whenever I need to.
Session persistence (as it is sometimes called) is also extremely
convienent for demos of multiple desktops (KDE, Gnome, liquid, IceWM).
Another helpful item is to use vncserver sessions on a laptop to deal with
resolution disparities. I use 1280x1024 when the laptop is docked and
1024x768 with a Virtual 1280x1024 when undocked. If not for vnc, I would have to
log out to change resolutions. This way I just kill the X session without logging
out of my vnc session.
If you are familiar with the Switch User feature on XP, this is similar in
the fact that multiple people can log into the machine simultaneously. The
difference is that Linux/Unix has always had that capability. This is
just another program to manage it.
Best vertis for you
This is a suite of wrapper tools written as bourne/bash shell scripts to manage VNC sessions on the same server and across the network to other servers. The toolkit is still under development but I am posting this because it is in a useful state. The utlilties are: Be the first to discover online hold em poker at Casinover
vncquick - Automatically starts/finds a vncserver session and connects to it. More than one session results in a menu that asks which session to choose.
vncmanager - a menu of options such as starting a new vncserver session, etc.
vnclient - a client side connection script that uses settings in $HOME/.vnc/client to connect to servers (still working on this)
vncfinder - a helper script to print out information about currently running vnc sessions
vncfindX - a helper script to find the path to Xwindows so that vncserver can run properly
what is depression
vncquick, vncfinder and vnclient have many options that can be viewed with -h. There may be better ways to accomplish these tasks so I am open to suggestions.
* When starting a vncserver session from kdm/xdm/gdm the window manager
inside of Xvnc is linked to the X session instead of the Xvnc
session. Consequently, when X closes so does the window manager
even though Xvnc stays running.
- Workaround - I have to start the server session from the command
line with vncquick -n. after that i can connect to it thru kdm w/o
problems.
Here is a gzipped tarball.
Eventually, I would like to add session persistence to XFree86 and use this suite to manage that feature. It should only require using the kernel framebuffer or writing a framebuffer driver for XFree86. libvncserver would be used to serve the RFB session and any rfb client could be used such as vnc and eventually TightVNC features would be added as well.
You can contact me at moreejt AT pcxperience.com, JT Moree
$Id: index.html,v 1.2 2002/11/04 22:49:40 moreejt Exp $