From an end-user's perspective: Yay! on all points.
Both client and server-side multithreading is a good idea if it is
necessary. However, it would be nice to be able to limit the number of
theads, especially server-side: if Xvnc spawns 24 (light) threads
continuously on a HPC server, I am afr
On 05/19/2011 11:46 AM, Pierre Ossman wrote:
> On Fri, 04 Mar 2011 10:07:09 +0100
> Sebastiaan Breedveld wrote:
>
>> On 03/03/2011 09:34 PM, Sebastiaan Breedveld wrote:
>>> Hi,
>>>
>>> Here is another patch. It adds a -resolutions argument with a list of
On 03/16/2011 09:50 PM, DRC wrote:
> http://www.virtualgl.org/DeveloperInfo/TigerVNCPreReleases
>
> -- Reverts default behavior of vncserver but adds a 'vncserver
> -autokill' option that will automatically kill Xvnc whenever xstartup exits.
>
Builds fine, runs fine (Linux 64). No comments from me
On 03/16/2011 09:59 PM, Eric Stadtherr wrote:
On Wed, 16 Mar 2011 15:50:53 -0500, DRC wrote:
http://www.virtualgl.org/DeveloperInfo/TigerVNCPreReleases
-- Reverts default behavior of vncserver but adds a 'vncserver
-autokill' option that will automatically kill Xvnc whenever xstartup exits.
On 03/15/2011 08:29 PM, DRC wrote:
> On 3/15/11 4:48 AM, Sebastiaan Breedveld wrote:
>> 1) The new vncserver script does something weird with -fg. When I use
>> this switch, xfce4 refuses to start with:
>>
>> "Unable to contact settings server. Failed to connect t
Hi,
3 points this time ;)
On 03/15/2011 09:45 AM, DRC wrote:
> I have lost track of the status of this. Can anyone still reproduce a
> problem with the latest build I uploaded on 3/10? If not, then I will
> spin a new build to incorporate the vncserver changes (reverting the
> default behavior
It seems that the -fg was implemented differently than expected:
diff between old and new
-system("$vncUserDir/xstartup >> " .
"edString($desktopLog) . " 2>&1 &");
+if ($opt{'-fg'}) {
+ system("$vncUserDir/xstartup >> " .
"edString($desktopLog) . " 2>&1"
On 03/09/2011 07:58 AM, DRC wrote:
Committed as 4343, with modifications. Please test.
Does not work right. If one of the checked arguments (SecurityTypes,
rfbauth, etc.) is preceeded by an argument that is NOT processed by the
vncserver script, but passed on to the Xvnc, the argument reading
On 03/09/2011 11:31 PM, Robert Goley wrote:
It should at least have one of the improvements you suggested
implemented. I understand not wanting to invest much with a new
viewer on the way but it sounds like it has a good bit to go right
now. That is not slighting his accomplishments in gettin
On 03/03/2011 01:18 PM, Adam Tkac wrote:
> On Thu, Mar 03, 2011 at 01:11:22PM +0100, Sebastiaan Breedveld wrote:
>> > 2) When using the VeNCrypt security type, the ~/.vnc/passwd is not
>>>> necessary, yet the user is asked to create one. Same when using the
>>&g
On 03/03/2011 09:34 PM, Sebastiaan Breedveld wrote:
Hi,
Here is another patch. It adds a -resolutions argument with a list of
resolutions to add to the default list:
Xvnc -resolutions "1264x900 1400x1500"
Of course this is a more flexible approach than specifying only 1 with
the
Hi,
Here is another patch. It adds a -resolutions argument with a list of
resolutions to add to the default list:
Xvnc -resolutions "1264x900 1400x1500"
Of course this is a more flexible approach than specifying only 1 with
the -geometry. Also, window managers tend to resize to the users'
sp
Will the new beta also include this patch? I am not able to build for
windows systems to test the patch, but I have users which can test the
windows viewer binary.
Greetings,
Sebastiaan
--
Free Software Download: Index
Hi,
Sure, here is the patch for the manpage.
On 03/03/2011 02:34 PM, Adam Tkac wrote:
> This extension of -inetd parameter seems fine for me. This functionality
> can be accepted to 1.1 after beta1 release.
>
> Btw would it be possible to also update Xvnc manpage to catch this
> extension, pleas
Hi,
In our environment, we have users that run persistent VNC sessions, and
on request through inetd. For ease of reminding, I like to give the
persistent users a low display number (e.g. 1-20). The problem is that a
new persistent user may have its display blocked by an inetd session.
Therefo
> 2) When using the VeNCrypt security type, the ~/.vnc/passwd is not
>> necessary, yet the user is asked to create one. Same when using the
>> securitytype none. The script now checks for the -SecurityType option
>> and checks wether VeNCrypt type or none is specified. (That is, I am in
>> the ass
This patch needs another line modified, to display the option when run
with vncserver -h.
The second patch is for the man-page (I have not updated the date of the
page, I will leave that to you).
Index: unix/vncserver
===
--- unix/
present by default. It is also not trivial to make one since each
distribution has its own way of configuring pam. I would suggest to
default to /etc/pam.d/vnc if present, otherwise use /etc/pam.d/login
(which is present on all systems).
Sebastiaan
Robert
On 03/01/2011 08:10 AM, Sebastiaan
ensitive) "VncAuth". If either of those
> conditions is true, then and only then should vncserver check for the
> existence of the VNC password.
>
Then how does it work? If I start:
Xvnc :10
then I read on the server:
client requests security type VeNCrypt
but the client tries to
On 03/01/2011 12:13 PM, DRC wrote:
>
> As far as checking for the VNC password, we're no longer requiring
> "VeNCrypt" to be specified in the -SecurityTypes parameter, so checking
> for that won't work. The correct approach is to check whether
> -SecurityTypes is not specified -- or -- whether -Se
tive) "VncAuth". If either of those
> conditions is true, then and only then should vncserver check for the
> existence of the VNC password.
>
Are you sure about that? If I run:
vncserver
and then connect, vncviewer still tries to authenticate with VncAuth.
I am using the Linux
Hi all,
This is actually a 2-in-1 patch (not sure if that is a good idea). I ran
into 2 problems with the old version:
1) When a VNC desktop is running, most users (accidentally) log out once
or twice, and then complain that their screen is black (or worse, has a
ghost image of the desktop). T
Hi,
On 02/25/2011 11:16 PM, Martin Koegler wrote:
> On Fri, Feb 25, 2011 at 09:52:48AM +0100, Sebastiaan Breedveld wrote:
>> Unfortunately, the radius configuration file contains a sectret
>> string to authenticate against the Radius server, so it should not
>> be world
On 02/25/2011 10:14 AM, DRC wrote:
> On 2/25/11 2:13 AM, Martin Koegler wrote:
>> The problem is, that some pam modules react differently, if they are
>> invoked by root or a normal user.
>>
>> The debian pam_unix eg. let normal users only verify their own
>> password and fails on any other user na
Hi,
On 02/25/2011 09:13 AM, Martin Koegler wrote:
> tigervnc currently only uses the auth section - account, session and
> password are ignored.
>
> Xvnc simply passes username& password to pam and waits for the
> result. I have tested it for example with the pam_krb5 module
> successfully.
>
> T
Dear list,
I am testing the 1.1 pre-beta (2/21/11) 64 bit Linux binary on an Ubuntu
Natty machine. According to previous posts, I start the VNC server as:
./Xvnc :4 -SecurityTypes=VeNCrypt,Plain -PlainUsers=sebastiaan
pam_service=vnc
which works fine when connecting with:
./vncviewer :4 -Securi
26 matches
Mail list logo
