Bovy, Stephen J napisal(a):
>
> 1) Is there any way to "detect" a Xvnc connection instance so that the
> xsession or xinitrc script only launches
> vncconfig for a Xvnc connection ???
It is tricky and may or may not work for your system - tou have to try it
out..
In my case, I tested the DISPLAY environment variable. All VNC sessions use
"local" displays so the DISPLAY variable has the form ":n.m" where n and m
are numbers. I have no real display on the server so I can safely assume
that all local displays are VNC displays (if you do have a real display, you
simply have to make an exception for :0).
In the case of remote X sessions to your machine, DISPLAY variable has the
form "machinename:n.m", where "machinename" is the address of the machine
the session was started from.
So I simply test if the DISPLAY variable starts with ":" - if yes, I run
vncconfig. Here is my mentioned 0100.vncconfig script:
#!/bin/sh
if { echo $DISPLAY | grep '^:' >/dev/null ; } then
/usr/local/bin/vncconfig -iconic &
fi
> 2) Does each Xvnc instance need its own copy of vncconfig or can
> vncconfig support multiple Xvnc ????
I think any VNC session requires it's own instance of vncconfig - at least
this is how I do it.
> 3) How does vncconfig know which Xvnc display to connect too ?
I think, like any X application, it simply attaches to the display specified
in the DISPLAY variable.
Regards,
Jaroslaw Rafa
[EMAIL PROTECTED]
--
Spam, wirusy, spyware... masz do6f? Jest alternatywa!
http://www.firefox.pl/ --- http://www.thunderbird.pl/
Szybciej. #atwiej. Bezpieczniej. Internet tak jak lubisz.
_______________________________________________
VNC-List mailing list
[email protected]
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list
