>> I use TightVNC to transport the user I/O between the server and the
>> clients.
>> :
>> Blah Blah Blah
>> :
>> I have written a number of scripts to help to automate and maintain my
>> setup. If anyone is interested I can make them available.
>Jim, I would be very interested and grateful for the scripts.
>
>Joe Fahy
Here is what I have so far:
I assign a display number to each user. I keep this display number in a
file called display in the .vnc sub-directory in the users home directory.
I use this in scripts where I need the user's display number.
I have a script called vncassign that creates the display file for each
user.
I have scripts that I use to start and stop the VNC servers for individual
users. These are called vnc800x600, vnc1024x768, and vncxxx. vncxxx
contains the common code and is called by vnc800x600 and vnc1024x768.
When called by a user : vnc800x600 stop|start|restart
When called by root : vnc800x600 stop|start|restart user
Typically my users do not start and stop their own VNC sessions. I keep
them running all the time.
I have a simple script to start and stop all the VNC servers called
vncservers.
The syntax is: vncservers stop|start|restart
I modify the xstartup script, in each users .vnc directory as follows:
#!/bin/sh
xrdb /usr/local/vnc/Xresources
xmodmap /usr/local/vnc/keymap
xterm &
win &
The Xresources file specifies an key map file for Win4Lin called Xvnc.xcode.
I have included that file. The file keymap maps the keys that are not
mapped by TightVNC.
I start an instance of xterm so that in I exit Win4Lin, using [Shift][F12],
I can restart it by typing win.
I have a simple script called listps to show the processes running for a
specific user and a script called showvnc to list the instances of Xvnc that
are currently running.
I run Samba on my Application Server machine. I have a share called \\vnc1.
Under that I have a directory called client and under that directories
called linux and win32.
In the win32 directory I have the configuration file for each vnc session.
and the latest vncviewer. This way I only have a shortcut on the Windows
clients and do not have to worry about updating individual machines when I
get a newer version of the viewer. I am not sure exactly how I plan to
handle remote machines. In that case I do not want to run vncviewer off the
network due to bandwidth limitations.
On the Linux clients I have modified /etc/sysconfig/desktop file as follows:
DESKTOP="VNC"
I have modified the file /etc/X11/xinit/XClients so that xdm will call my
script, called VNC when starting X windows.
The user runs a script called vnc1. This script downloads the latest
version of vncviewer, the users VNC password file, and the script VNC, and
then calls startx. Again here my hope is to minimize maintenance at the
client machine.
The script vnc1 could use some work. For one thing it asks the user for
their Samba password and displays the entered text.
I hope this is useful and would be grateful to hear any suggestions for
improvement.
Jim Daleo
VNCScripts.zip
