I appreciate the responses to my help request even though they were not
able to resolve my issue.
As some vnc users of xinet have found, xstartup is not called when Xvnc
is initiated by the xinet service. This is a problem for those that
want cut/copy/paste capabilities through vncconfig, which is called from
the xstartup script. I do not know why xstartup is not called, nor has
anyone fully explained why. I am not a system admin only a simple
professor and part time consultant trying to operate economically.
I did find a work around to get vncconfig loaded when a user logs in
through a remote connection using xinet on a Redhat EL4 server. I hope
this helps others out that have struggled with this.
I created the following shell script to execute from the graphics
display environment autostart after the session is started.
#!/bin/bash
list=`pgrep -U $USER Xvnc`
#echo $list
if [ {#list}>0 ]; then
# echo $list
vncconfig
fi
The pgrep function looks at the processes for the $USER named Xvnc.
Recall Xvnc is run from the xinet service. If the list is > 0 a remote
session has started so load vncconfig. You might need to specify hard
location /XXX/vncprograms/vncconfig. You can also add vncconfig options
to this.
I am using KDE GDM on this server with individual xinet vnc connections
tied to specific users. That is why the $USER is in the pgrep. One
using a different xinet vnc script will need to modify this to fit their
environment. See man -k pgrep for more information. I copied a
version of this shell script to each users $HOME/.kde/autostart
directory, specified the run setting chmod 744 vncconfigload.sh, and was
done.
The drawback here is that each user has to have this script in
their .kde/autostart directory on a system. If someone can tell me how
to make this automatically work for all users from one location not
individual, I would appreciate it.
I think this will work for Gnome but do not know where to put it in a
Gnome autostart location.
Any improvements or a better idea would be appreciated.
Thank you
Joe
P.S. James, this or a better version of this might be helpful in the
xinet/inet.d section of the documentation
James Weatherall wrote:
> Hi Joe,
>
> Text copy & paste requires that vncconfig be running in the VNC X desktop.
>
> Regards,
>
> Wez @ RealVNC Ltd.
>
>
>
>> -----Original Message-----
>> From: [EMAIL PROTECTED]
>> [mailto:[EMAIL PROTECTED] On Behalf Of Financial
>> Systems & Economic Analytics
>> Sent: 24 April 2006 12:44
>> To: [email protected]
>> Subject: cut copy and paste VNC Enterprise and xinet
>>
>> How does one get the cut copy and paste to automatically work
>> with VNC
>> enterprise? The Xstartup script does not get executed when
>> using xinet
>> on Redhat Linux RHEL4.
>>
>> Thank you
>> Joe
>>
>>
>> --
>> _______________________________________________
>> VNC-List mailing list
>> [email protected]
>> To remove yourself from the list visit:
>> http://www.realvnc.com/mailman/listinfo/vnc-list
>>
>>
>
>
>
--
_______________________________________________
VNC-List mailing list
[email protected]
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list
