You can't expect TurboVNC to not ever change. This change brings our
behavior in line with TigerVNC and RealVNC. Those platforms allow you
to specify the remote desktop name, which will appear in the titlebar of
the viewer when you connect. Previously, TurboVNC used a less
descriptive desktop name ("X") and would always prepend "TurboVNC" to
it, regardless of whether the desktop name was overridden. It now uses
a default desktop name that already contains "TurboVNC", so overriding
the desktop name works as one would expect. The output of the script is
in line with the output of the equivalent script in RealVNC and
TigerVNC. It should not be that difficult to handle both the new and
the old output.
I have no plans to change this again in the future, but I can't
guarantee that it will be this way forever, either. TurboVNC changes
when it needs to change.
On 10/10/12 8:29 AM, Arthur Huillet wrote:
> Hello,
>
> I'm using some scripts to parse the output of the vncserver script, to
> retrieve
> the DISPLAY number.
>
> In TurboVNC 1.1, this is what the output looks like:
>
> New 'X' desktop is myhostname:9
>
> In the latest pre-release build, this is what it looks like:
>
> Desktop 'TurboVNC: myhostname:4 (sxdauk)' started on display
> myhostname:4
>
> Is this change expected? Would you be willing to revert it? If not, can I
> count
> on it not changing (too much) in the future? If not, what's the proper way to
> retrieve the display number from a script calling "vncserver" ?
------------------------------------------------------------------------------
Don't let slow site performance ruin your business. Deploy New Relic APM
Deploy New Relic app performance management and know exactly
what is happening inside your Ruby, Python, PHP, Java, and .NET app
Try New Relic at no cost today and get our sweet Data Nerd shirt too!
http://p.sf.net/sfu/newrelic-dev2dev
_______________________________________________
VirtualGL-Users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/virtualgl-users
