A Big Thanks to every who has supported this issue.
As the below mail said, new version of Vnc with Xinetd support saving of
session for the future use.
It works for me too. Now I am able to reopen the closed session again.
Configuration details below
service vnc-server
{
disable = no
socket_type = stream
protocol = tcp
wait = yes
user = root
server = /usr/bin/Xvnc
log_on_failure += USERID
server_args = -inetd -query localhost -once -geometry
800x600 /
-depth 16 securitytypes=none
}
Thanks again.
Gurjit Dhillon
-----Original Message-----
From: James Weatherall [mailto:[EMAIL PROTECTED]
Sent: Friday, February 16, 2007 9:08 AM
To: Dhillon, Gurjit; 'Peter Rosin'; 'Corne Beerse'
Cc: vnc-list@realvnc.com
Subject: RE: How to restore the session if vnc server is configure as
daemon mode xinetd
Hi Dhillon,
Recent VNC Server releases support xinetd wait=yes, so if you upgrade
your
VNC installation then you should be able to run things that way.
Cheers,
Wez @ RealVNC Ltd.
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Dhillon, Gurjit
> Sent: 16 February 2007 13:04
> To: Peter Rosin; Corne Beerse
> Cc: vnc-list@realvnc.com
> Subject: RE: How to restore the session if vnc server is
> configure as daemon mode xinetd
>
> I don't what this options does actually, but I have tried
> wait = yes, it
> was no earlier.
>
> I didn't got any screen if I do that, even if I do telnet it just wait
> to give the response.
>
> [EMAIL PROTECTED] root]# telnet localhost 5985
> Trying 127.0.0.1...
> Connected to localhost.localdomain (127.0.0.1).
> Escape character is '^]'.
>
> And if I change it back to wait = no , I get the telnet
> console and vnc
> session too
>
> [EMAIL PROTECTED] root]# telnet localhost 5985
> Trying 127.0.0.1...
> Connected to localhost.localdomain (127.0.0.1).
> Escape character is '^]'.
> RFB 003.003
>
> Thanks for all your response. But I am in blank now, I have
> made all my
> efforts to get this work,
>
> Gurjit Dhillon
>
> -----Original Message-----
> From: Peter Rosin [mailto:[EMAIL PROTECTED]
> Sent: Friday, February 16, 2007 7:52 AM
> To: Corne Beerse
> Cc: Dhillon, Gurjit; vnc-list@realvnc.com
> Subject: Re: How to restore the session if vnc server is configure as
> daemon mode xinetd
>
> On Fri, Feb 16, 2007 at 11:22:45AM +0100, Corne Beerse wrote:
> > Dhillon, Gurjit wrote:
> >
> > >I have set up vnc as a daemon mode through xinetd, it is working
> fine.
> > >
> > >
> > >
> > Great.
> >
> > >User give ipaddress and the predefined port number to
> connect the vnc
> > >server. The only difference is now user doesn't need to login the
> Linux
> > >server and generate the port number to connect the server through
> vnc,
> > >now it is asking for login and password to connect the server. But
> here
> > >if user close the session after login or after his job
> done, and want
> to
> > >work in the same session after some day or some time, they are not
> able
> > >to do that.
> > >
> > >
> > >
> > Thats one of the nice features of inetd (or xinetd): As soon as the
> > connection ends, the processes are cleared.
> > If you want re-entrant vnc-sessions, you cannot use inetd or xinetd.
>
> Bzzt, not entierly true. You should investigate the wait option of
> inetd (wait = yes for xinetd). It is very possible to have a server
> controlled by (x)inetd survive a disconnected connection.
>
> That said, I don't know if any vnc server actually supports this mode
> of operation, but I'd be surprised if they didn't.
>
> [snip]
>
> Cheers,
> Peter
> _______________________________________________
> 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
