Joe:
In My Humble Opinion, reconfiguring the X server is not really a subject for
this list. Since you have RHEL, you have a support contract with RedHat. I
suggest you call one of their engineers and get them to help you fix this
problem. That's what Tech Support is for. :-)
John
(Not employed or affiliated with RealVNC other than as a happy user!)
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Behalf Of Financial Systems & Economic Analytics
Sent: Wednesday, February 01, 2006 11:22 AM
To: S. I. Becker
Cc: vnc-list@realvnc.com
Subject: Re: SSh-agent not dying after vnc viewer
exit/logoff/logout/disconnect
James and Stewart
I appreciate your patience with me. I am not a sysadmin and do not
know linux very well. Been using for a year, mainly for the stability
so I can run research projects that take days to process and to store
data that I have collected.
I am going to try and combine both your threads here.
Summary
Systems RHEL 4 for vncserver, WinXP for viewer.
VNC config, standard config for xinetd using realvnc mail list
instructions. config and startup files in /etc/vnc.
RHEL 4 sessions using KDE as the desktop environment (maybe gnome in the
background, that is somthing I do not know).
Symptons,
Open viewer on the XP maching and connect to server using username,
password. Server starts Xvnc and a ssh-agent process.
Exit, disconnet from server, Xvnc stops normally, ssh-agent does not exit.
You both have suggested the following
James: You probably want to configure your SSH client not to use
ssh-agent, since it appears not to be terminating itself.
S.I.: If it's ssh-agent on the on the _server_ that is causing a
problem, then it may be because X is starting ssh-agent when it starts,
but not closing it when it exits. In that case, you need to check your
scripts that run when X closes.
I think well all agree that I need to reconfigure X or kde not not use
ssh-agent or to perform an ssh-agent -k upon exit or maybe after the
XVnc is up and running?
The problem is that I do not have a clue how to do this or really where
to start. I did find in a google search that kde has an a
autostart feature and I think a shutdown feature
(~/home/userhome/.kde/autostart). I would have to put a script for
ssh-agent -k in each users .kde directory unless there is a global .kde
directory.
could I put the ssh-agent -k in the xstartup after the call to the
window manager? as
dvm &
ssh-agent -k &
Any thoughts, suggestions, or other comments are greatly appreciated.
Thank you
Joe
S. I. Becker wrote:
> Joe,
>
> I've been assuming that you are running the VNC session through an ssh
> encrypted tunnel, and that ssh-agent on the _viewer_ machine that you
> are using to store your passwords isn't closing properly (although
> thinking a bit harder, you wouldn't want it to close on the viewer
> machine until you log off there). If it's ssh-agent on the on the
> _server_ that is causing a problem, then it may be because X is
> starting ssh-agent when it starts, but not closing it when it exits.
> In that case, you need to check your scripts that run when X closes.
>
> Stewart
> ----- Original Message ----- From: "Financial Systems & Economic
> Analytics" <[EMAIL PROTECTED]>
> To: "S. I. Becker" <[EMAIL PROTECTED]>
> Cc: <vnc-list@realvnc.com>
> Sent: Wednesday, February 01, 2006 3:00 PM
> Subject: Re: SSh-agent not dying after vnc viewer
> exit/logoff/logout/disconnect
>
>
>> On my system, I am using xinetd following the vnc mail list example.
>>
>> So,
>> When is the ssh getting call when a vnc session starts?
>>
>> How to I set up a script or set the ssh session to die after a short
>> time (say 60 secs)?
>>
>>
>> Thank you
>> Joe
>>
>>
>> S. I. Becker wrote:
>>>
>>>
>>>> Stewart,
>>>>
>>>> Ssh clients hold the connection open so long as there is something
>>>> using it,
>>>> in this case a forwarded port. There's no way that the client could
>>>> exit
>>>> without causing the forwarded port to close, too.
>>>>
>>>
>>> James,
>>>
>>> That's the point! You initiate the ssh session, with a shell/script
>>> that will just exit after, say, 60 seconds. In the mean time you set
>>> up the tunnelled VNC session. The ssh session exits when the time is
>>> up, but is held open by the open tunnelled port(s). Then when you do
>>> close the VNC session, the ssh session closes too because there is now
>>> nothing to keep it open, which is what I thought was wanted.
>>>
>>> Stewart
>>>
>>>
>>
>> --
>>
>
>
>
----------------------------------------------------------------------------
----
>
>
>
>> On my system, I am using xinetd following the vnc mail list example.
>>
>> So,
>> When is the ssh getting call when a vnc session starts?
>>
>> How to I set up a script or set the ssh session to die after a short
>> time (say 60 secs)?
>>
>>
>> Thank you
>> Joe
>>
>>
>> S. I. Becker wrote:
>>
>>
>>
>> Stewart,
>>
>> Ssh clients hold the connection open so long as there is something
>> using it,
>> in this case a forwarded port. There's no way that the client
>> could exit
>> without causing the forwarded port to close, too.
>>
>>
>>
>> James,
>>
>> That's the point! You initiate the ssh session, with a shell/script
>> that will just exit after, say, 60 seconds. In the mean time you set
>> up the tunnelled VNC session. The ssh session exits when the time is
>> up, but is held open by the open tunnelled port(s). Then when you do
>> close the VNC session, the ssh session closes too because there is
>> now nothing to keep it open, which is what I thought was wanted.
>>
>> Stewart
>>
>>
>>
>>
>>
>> --
>>
>
>
>
--
_______________________________________________
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list
_______________________________________________
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list
