Re: TightVNC session timeout

[Rafael G. <rg...@gm...>]

Hi,

First of all, thanks a lot for your comments. After going through lots of
logs and debugging, I have realized that my VNC sessions are terminated due
to an apache restart. Every sunday, the apache logs are rotated (a cron job
calls logrotate) and httpd is killed -HUP. And exactly at this moment, every
running IceWM session is terminated. I still didn't find out why this
happens, but this is the reason.

Although VNC sessions are created through an PHP script, if I run "ps -ef" I
see that their parent pid is 1, so they should not be attached to the httpd
process (at least in theory). However, if I create one VNC session through
PHP and the other manually (running the same command in the shell session),
the PHP started session is terminated whenever I "kill -HUP httpd" while the
manually started session keeps running. The most funny thing is that the PHP
process calls the vncserver script, which calls Xvnc. And, as far as I
understood, XVnc is the one that creates the window manager processes (in my
case, IceWM). But when I "kill -HUP httpd", Xvnc processes keep running,
while IceWM terminates. I have also checked the files that these processes
have opened and there are no common files... So, I am still a bit lost. I
have tried to call vncserver with "nohup vncserver" from the PHP script, but
the same happens...

Any suggestions?

Best regards,

Rafael Guimarães

2009/10/20 Constantin Kaplinsky <co...@ti...>

> Hello Rafael,
>
> >>>>> Rafael Guimaraes wrote:
>
> > I have built a visualization server using TightVNC and VirtualGL, just as
> > the solution presented at www.virtualgl.org. In this server, I am able
> to
> > launch several remote sessions using TightVNC. Each of the these sessions
> > uses a different display number (:1, :2, :3 ...). However, I am facing
> some
> > problems with session timeout. If I create a TightVNC session and do not
> use
> > it for about 4 days, the window manager of this session (i.e. its
> processes)
> > is terminated. In this case, after these 4 days, if I connect to the VNC
> > session, I can only see the X cursor on a gray background (no window
> > manager, just Xvnc).
> >
> > I am currently using IceWM, but I have also tried with JWM and I had the
> > same problem. Does anybody know what might be the problem? Is there some
> > kind of timeout in TightVNC that may be producing the behavior?
>
> I don't think there is such a timeout in Xvnc.
>
> Actually, I have a Debian machine with Xtightvnc (Xvnc from the TightVNC
> distribution) running for weeks and months and I never experienced such
> a problem. By the way, I use IceWM as well.
>
> --
> With Best Wishes,
> Constantin
>