> -----Original Message-----
> From: Lee Allen [mailto:[EMAIL PROTECTED]]
> I know vncserver can start applications. I must use Xvnc in
> -inetd mode, to
> support multiple users and non-persistent sessions.
>
> I was just thinking, since inetd starts Xvnc with a user
> name, it would be
> nice if it could start the apps specified in .vnc/xstartup or
> xinitrc, and
> not require XDMCP. In my case, the login step required by XDMCP is
> unnecessary ... but unavoidable.
>
If security is not an issue, it is no problem to have inetd start Xvnc
including some apps. There are several routes to do so. My idea:
Setup a user ('specialuser') and its vncserver setup, including dedicated
~/.vnc/xstartup scripts and vnc-password. Then create an inetd 'commandline'
as follows:
special-vnc stream tcp nowait specialuser /usr/local/bin/vncserver vncserver
-inetd
(the above is 1 line). You might add options like '-once' or geometry or
depth specifications. However, you can also create a special vncserver
script (it's perl, so you must be able to create one) Best NOT to specify
the -inetd in the scipt but have that specified from the commandline and
pass trough to Xvnc, for easy testing.
Note: inetd will start a new session for every connection, so if the sessins
do not end automatically, you should specify -once to clear lost sessions.
As for the XDMCP options: They are not required if you use inetd, it's just
CBee
_______________________________________________
VNC-List mailing list
[EMAIL PROTECTED]
http://www.realvnc.com/mailman/listinfo/vnc-list
