From: Phillip Pi <ph...@ap...> - 2002-04-08 20:21:18
|
I am trying to install the package (source), but I noticed it seems to require root access. Is there a way to install this without root access since the box I am using is not mine? Thank you in advance. :) -- "Lay a stick of bubble gum on an anthill for instant Siamese Ant Twins." --unknown -- /\___/\ Phillip Pi (Ant) / /\ /\ \ E-Mail: ph...@ea... or ph...@ap... | |. .| | \ _ / The Ant Farm: http://antfarm.home.dhs.org ( ) ICQ UIN: 2223658 |
From: Phillip Pi <ph...@ap...> - 2002-04-09 02:59:39
|
Actually, is there a way to install TightVNC without affecting my other VNC? I tried RPMs, but I had too many dependencies and conflicts. I would like to leave my original VNC alone. Can I compile the VNC locally (in a directory) without root access? I am a Linux newbie so I am not sure if this is complex. On Mon, 8 Apr 2002, Phillip Pi wrote: > I am trying to install the package (source), but I noticed it seems to > require root access. Is there a way to install this without root access > since the box I am using is not mine? > > Thank you in advance. :) |
From: Constantin K. <co...@ce...> - 2002-04-09 15:45:05
|
Hello Phillip, >>>>> "PP" == Phillip Pi <ph...@ap...> writes: >> I am trying to install the package (source), but I noticed it seems >> to require root access. Is there a way to install this without root >> access since the box I am using is not mine? There is a way. You'll have to copy files into some place under your home directory and edit the vncserver script to set correct paths for Xvnc executable and Java classes directory. -- With Best Wishes, Constantin |
From: Phillip Pi <ph...@ap...> - 2002-04-09 16:22:13
|
On 9 Apr 2002, Constantin Kaplinsky wrote: > Hello Phillip, > > >>>>> "PP" == Phillip Pi <ph...@ap...> writes: > > >> I am trying to install the package (source), but I noticed it seems > >> to require root access. Is there a way to install this without root > >> access since the box I am using is not mine? > > There is a way. You'll have to copy files into some place under your > home directory and edit the vncserver script to set correct paths for > Xvnc executable and Java classes directory. Is there a lot of paths to change in the scripts? I am only interested in the server and Xvnc viewer. |
From: Constantin K. <co...@ce...> - 2002-04-09 17:32:46
|
>>>>> "PP" == Phillip Pi <ph...@ap...> writes: >> There is a way. You'll have to copy files into some place under >> your home directory and edit the vncserver script to set correct >> paths for Xvnc executable and Java classes directory. PP> Is there a lot of paths to change in the scripts? I am only PP> interested in the server and Xvnc viewer. No, just a few. Most important to set explicit path to Xvnc. E.g. change "Xvnc" to something like "$ENV{HOME}/bin/Xvnc". -- With Best Wishes, Constantin |
From: Phillip Pi <ph...@ap...> - 2002-04-10 04:30:24
|
> >> There is a way. You'll have to copy files into some place under > >> your home directory and edit the vncserver script to set correct > >> paths for Xvnc executable and Java classes directory. > > PP> Is there a lot of paths to change in the scripts? I am only > PP> interested in the server and Xvnc viewer. > > No, just a few. Most important to set explicit path to Xvnc. > E.g. change "Xvnc" to something like "$ENV{HOME}/bin/Xvnc". I noticed I might need the libraries too. Will this be a problem for compilation? |
From: Constantin K. <co...@ce...> - 2002-04-10 06:29:59
|
Hello Phillip, >>>>> "PP" == Phillip Pi <ph...@ap...> writes: >> >> There is a way. You'll have to copy files into some place under >> >> your home directory and edit the vncserver script to set correct >> >> paths for Xvnc executable and Java classes directory. >> PP> Is there a lot of paths to change in the scripts? I am only PP> interested in the server and Xvnc viewer. >> >> No, just a few. Most important to set explicit path to Xvnc. E.g. >> change "Xvnc" to something like "$ENV{HOME}/bin/Xvnc". PP> I noticed I might need the libraries too. Will this be a problem PP> for compilation? Compilation never required root privilegies, so there should not be any problems with compilation. -- With Best Wishes, Constantin |
From: Phillip Pi <ph...@ap...> - 2002-04-10 06:38:38
|
On 10 Apr 2002, Constantin Kaplinsky wrote: > Hello Phillip, > > >>>>> "PP" == Phillip Pi <ph...@ap...> writes: > > >> >> There is a way. You'll have to copy files into some place under > >> >> your home directory and edit the vncserver script to set correct > >> >> paths for Xvnc executable and Java classes directory. > >> > PP> Is there a lot of paths to change in the scripts? I am only > PP> interested in the server and Xvnc viewer. > >> > >> No, just a few. Most important to set explicit path to Xvnc. E.g. > >> change "Xvnc" to something like "$ENV{HOME}/bin/Xvnc". > > PP> I noticed I might need the libraries too. Will this be a problem > PP> for compilation? > > Compilation never required root privilegies, so there should not be > any problems with compilation. Awesome, I think I got it compiled and working! I am wondering. Has anyone tried TightVNC over a dial-up modem connection that goes up to 3.0 KB/sec? I tried using Best Compression, 8-bit colors, 640x480 resolution, simple X desktop, etc. It still seems slow. Are there anything else to make it faster? |
From: Constantin K. <co...@ce...> - 2002-04-10 08:01:00
|
>>>>> "PP" == Phillip Pi <ph...@ap...> writes: PP> Awesome, I think I got it compiled and working! I am wondering. PP> Has anyone tried TightVNC over a dial-up modem connection that PP> goes up to 3.0 KB/sec? I tried using Best Compression, 8-bit PP> colors, 640x480 resolution, simple X desktop, etc. It still seems PP> slow. Are there anything else to make it faster? Please take a look at server logs under $HOME/.vnc/ directory, make sure the clients really use the Tight encoding (see the statistics in the logs). -- With Best Wishes, Constantin |
From: Phillip Pi <ph...@ap...> - 2002-04-10 08:24:23
|
> PP> Awesome, I think I got it compiled and working! I am wondering. > PP> Has anyone tried TightVNC over a dial-up modem connection that > PP> goes up to 3.0 KB/sec? I tried using Best Compression, 8-bit > PP> colors, 640x480 resolution, simple X desktop, etc. It still seems > PP> slow. Are there anything else to make it faster? > > Please take a look at server logs under $HOME/.vnc/ directory, make > sure the clients really use the Tight encoding (see the statistics in > the logs). What do you think from my pasted log? Can I simplify more? :) [edited the logs to remove server/IP addresses] 10/04/02 01:16:19 Xvnc version 3.3.3r2+tight1.2.3 10/04/02 01:16:19 Copyright (C) AT&T Laboratories Cambridge. 10/04/02 01:16:19 All Rights Reserved. 10/04/02 01:16:19 See http://www.uk.research.att.com/vnc for information on VNC 10/04/02 01:16:19 Desktop name 'X' (xxxxxxx:1) 10/04/02 01:16:19 Protocol version supported 3.3 10/04/02 01:16:19 Listening for VNC connections on TCP port 5901 10/04/02 01:16:19 Listening for HTTP connections on TCP port 5801 10/04/02 01:16:19 URL http://xxxxxxx:5801 _FontTransSocketUNIXConnect: Can't connect: errno = 111 failed to set default font path 'unix/:7100' Fatal server error: could not open default font 'fixed' 10/04/02 01:16:20 Xvnc version 3.3.3r2+tight1.2.3 10/04/02 01:16:20 Copyright (C) AT&T Laboratories Cambridge. 10/04/02 01:16:20 All Rights Reserved. 10/04/02 01:16:20 See http://www.uk.research.att.com/vnc for information on VNC 10/04/02 01:16:20 Desktop name 'X' (xxxxxxx:1) 10/04/02 01:16:20 Protocol version supported 3.3 10/04/02 01:16:20 Listening for VNC connections on TCP port 5901 10/04/02 01:16:20 Listening for HTTP connections on TCP port 5801 10/04/02 01:16:20 URL http://xxxxxxxxxxx:5801 xrdb: No such file or directory xrdb: can't open file '/home/philpi/.Xresources' _IceTransmkdir: Owner of /tmp/.ICE-unix should be set to root SESSION_MANAGER=local/xxxxxxx:/tmp/.ICE-unix/6554 1:16am up 141 days, 12:34, 14 users, load average: 0.36, 0.13, 0.03 [removed who's online list] stdin: is not a tty aumix: error opening mixer Gnome-Message: gnome_execute_async_with_env_fds: returning -1 Gnome-Message: gnome_execute_async_with_env_fds: returning -1 Gtk-WARNING **: gtk_signal_disconnect_by_data(): could not find handler containing data (0x8167E70) 10/04/02 01:17:48 Got connection from client 209.245.78.xxx 10/04/02 01:17:48 Protocol version 3.5 10/04/02 01:17:48 Ignoring minor version mismatch 10/04/02 01:17:51 Pixel format for client 209.245.78.xxx: 10/04/02 01:17:51 8 bpp, depth 8 10/04/02 01:17:51 true colour: max r 7 g 7 b 3, shift r 0 g 3 b 6 10/04/02 01:17:51 Using tight encoding for client 209.245.78.xxx 10/04/02 01:17:51 rfbProcessClientNormalMessage: ignoring unknown encoding 8 10/04/02 01:17:51 Using compression level 9 for client 209.245.78.xxx 10/04/02 01:17:51 Enabling X-style cursor updates for client 209.245.78.xxx 10/04/02 01:17:51 Using image quality level 9 for client 209.245.78.xxx 10/04/02 01:17:51 Enabling LastRect protocol extension for client 209.245.78.xxx 10/04/02 01:18:07 Client 209.245.78.xxx gone 10/04/02 01:18:07 Statistics: 10/04/02 01:18:07 key events received 0, pointer events 139 10/04/02 01:18:07 framebuffer updates 8, rectangles 1350, bytes 25869 10/04/02 01:18:07 LastRect markers 3, bytes 36 10/04/02 01:18:07 cursor shape updates 4, bytes 328 10/04/02 01:18:07 copyRect rectangles 131, bytes 2096 10/04/02 01:18:07 tight rectangles 1212, bytes 23409 10/04/02 01:18:07 raw bytes equivalent 968249, compression ratio 41.362254 xterm: fatal IO error 32 (Broken pipe) or KillClient on X server ":1.0" X connection to :1.0 broken (explicit kill or server shutdown). X connection to :1.0 broken (explicit kill or server shutdown). Gdk-ERROR **: X connection to :1.0 broken (explicit kill or server shutdown). Gdk-ERROR **: X connection to :1.0 broken (explicit kill or server shutdown). Gdk-ERROR **: X connection to :1.0 broken (explicit kill or server shutdown). Gdk-ERROR **: X connection to :1.0 broken (explicit kill or server shutdown). |
From: Constantin K. <co...@ce...> - 2002-05-11 09:25:11
|
Hello Phillip, >>>>> "PP" == Phillip Pi <ph...@ap...> writes: PP> Awesome, I think I got it compiled and working! I am wondering. PP> Has anyone tried TightVNC over a dial-up modem connection that PP> goes up to 3.0 KB/sec? I tried using Best Compression, 8-bit PP> colors, 640x480 resolution, simple X desktop, etc. It still seems PP> slow. Are there anything else to make it faster? >> Please take a look at server logs under $HOME/.vnc/ directory, make >> sure the clients really use the Tight encoding (see the statistics >> in the logs). PP> What do you think from my pasted log? Can I simplify more? :) PP> [edited the logs to remove server/IP addresses] Ok, let me comment the logs. PP> 10/04/02 01:17:48 Got connection from client 209.245.78.xxx PP> 10/04/02 01:17:48 Protocol version 3.5 PP> 10/04/02 01:17:48 Ignoring minor version mismatch PP> 10/04/02 01:17:51 Pixel format for client 209.245.78.xxx: PP> 10/04/02 01:17:51 8 bpp, depth 8 PP> 10/04/02 01:17:51 true colour: max r 7 g 7 b 3, shift r 0 g 3 b 6 PP> 10/04/02 01:17:51 Using tight encoding for client 209.245.78.xxx PP> 10/04/02 01:17:51 rfbProcessClientNormalMessage: ignoring unknown encoding 8 PP> 10/04/02 01:17:51 Using compression level 9 for client 209.245.78.xxx PP> 10/04/02 01:17:51 Enabling X-style cursor updates for client 209.245.78.xxx PP> 10/04/02 01:17:51 Using image quality level 9 for client 209.245.78.xxx PP> 10/04/02 01:17:51 Enabling LastRect protocol extension for client 209.245.78.xxx The client was connected and requested Tight encoding and 8 bpp color format. PP> 10/04/02 01:18:07 Client 209.245.78.xxx gone PP> 10/04/02 01:18:07 Statistics: PP> 10/04/02 01:18:07 key events received 0, pointer events 139 PP> 10/04/02 01:18:07 framebuffer updates 8, rectangles 1350, bytes 25869 PP> 10/04/02 01:18:07 LastRect markers 3, bytes 36 PP> 10/04/02 01:18:07 cursor shape updates 4, bytes 328 PP> 10/04/02 01:18:07 copyRect rectangles 131, bytes 2096 PP> 10/04/02 01:18:07 tight rectangles 1212, bytes 23409 PP> 10/04/02 01:18:07 raw bytes equivalent 968249, compression ratio 41.362254 Well, the connection was only 16 seconds long, and the server sent 25869 bytes to the client. The strange thing here is that the updates are very small (1212 rectangles, about 19 compressed bytes each rectangle on average, where 12 bytes is the size of rectangle header data, regardless of the encoding). Another interesting issue is that there were many CopyRect rectangles. I think that low performance here is not related to the encoder or pixel format. When there are so many _very_ small rectangles, they would be encoded inefficiently by any encoder, due to the nature of the RFB protocol. I think this behaviour (sending too many small rectangles) is application specific. What application did you use on the server during that session? I planned to work on improvement for Xvnc that could combine many small rectangles together, to improve average throughoutput, but had no possibility to find the time / money support for the project. Maybe I'll work on that at some point, but I would not promise to do it really soon. -- With Best Wishes, Constantin |
From: Phillip Pi <ph...@ap...> - 2002-05-11 15:32:43
|
> PP> Awesome, I think I got it compiled and working! I am wondering. > PP> Has anyone tried TightVNC over a dial-up modem connection that > PP> goes up to 3.0 KB/sec? I tried using Best Compression, 8-bit > PP> colors, 640x480 resolution, simple X desktop, etc. It still seems > PP> slow. Are there anything else to make it faster? > > >> Please take a look at server logs under $HOME/.vnc/ directory, make > >> sure the clients really use the Tight encoding (see the statistics > >> in the logs). > > PP> What do you think from my pasted log? Can I simplify more? :) > > PP> [edited the logs to remove server/IP addresses] > > Ok, let me comment the logs. > > PP> 10/04/02 01:17:48 Got connection from client 209.245.78.xxx > PP> 10/04/02 01:17:48 Protocol version 3.5 > PP> 10/04/02 01:17:48 Ignoring minor version mismatch > PP> 10/04/02 01:17:51 Pixel format for client 209.245.78.xxx: > PP> 10/04/02 01:17:51 8 bpp, depth 8 > PP> 10/04/02 01:17:51 true colour: max r 7 g 7 b 3, shift r 0 g 3 b 6 > PP> 10/04/02 01:17:51 Using tight encoding for client 209.245.78.xxx > PP> 10/04/02 01:17:51 rfbProcessClientNormalMessage: ignoring unknown encoding 8 > PP> 10/04/02 01:17:51 Using compression level 9 for client 209.245.78.xxx > PP> 10/04/02 01:17:51 Enabling X-style cursor updates for client 209.245.78.xxx > PP> 10/04/02 01:17:51 Using image quality level 9 for client 209.245.78.xxx > PP> 10/04/02 01:17:51 Enabling LastRect protocol extension for client 209.245.78.xxx > > The client was connected and requested Tight encoding and 8 bpp color > format. > > PP> 10/04/02 01:18:07 Client 209.245.78.xxx gone > PP> 10/04/02 01:18:07 Statistics: > PP> 10/04/02 01:18:07 key events received 0, pointer events 139 > PP> 10/04/02 01:18:07 framebuffer updates 8, rectangles 1350, bytes 25869 > PP> 10/04/02 01:18:07 LastRect markers 3, bytes 36 > PP> 10/04/02 01:18:07 cursor shape updates 4, bytes 328 > PP> 10/04/02 01:18:07 copyRect rectangles 131, bytes 2096 > PP> 10/04/02 01:18:07 tight rectangles 1212, bytes 23409 > PP> 10/04/02 01:18:07 raw bytes equivalent 968249, compression ratio 41.362254 > > Well, the connection was only 16 seconds long, and the server sent > 25869 bytes to the client. The strange thing here is that the updates > are very small (1212 rectangles, about 19 compressed bytes each > rectangle on average, where 12 bytes is the size of rectangle header > data, regardless of the encoding). Another interesting issue is that > there were many CopyRect rectangles. > > I think that low performance here is not related to the encoder or > pixel format. When there are so many _very_ small rectangles, they > would be encoded inefficiently by any encoder, due to the nature of > the RFB protocol. I think this behaviour (sending too many small > rectangles) is application specific. What application did you use on > the server during that session? I think I mainly used GNOME with the default theme, Pan, Lopster, etc. I used a low resolution and color depth to keep speed decent. > I planned to work on improvement for Xvnc that could combine many > small rectangles together, to improve average throughoutput, but had > no possibility to find the time / money support for the project. Maybe > I'll work on that at some point, but I would not promise to do it > really soon. OK. If there are any tips in improving the speed, then please feel free to shoot. |
From: Phillip Pi <ph...@ap...> - 2002-04-22 20:40:35
|
http://slashdot.org/article.pl?sid=02/04/22/0740239&mode=thread&tid=99 DOH! -- "No, I'd prefer a cooler WITHOUT an ant-door, thank you..." --unknown -- /\___/\ Phillip Pi (Ant) / /\ /\ \ E-Mail: ph...@ea... or ph...@ap... | |. .| | \ _ / The Ant Farm: http://antfarm.home.dhs.org ( ) ICQ UIN: 2223658 |
From: Phillip Pi <ph...@ap...> - 2002-04-30 22:26:22
|
I am using TightVNC and I can't seem to tell the speed difference between 24-bit and 8-bit color depths (both are at 1024x768 resolutions with Gnome) even with the best compression enabled. In theory, shouldn't I notice a speed improvement? I am trying this on a T1 connection (less than 50ms pings and about 18 hops). Am I missing something? Thank you in advance. :) -- "Now I have you where I want you... where is my jar of Bull ants?" --unknown -- /\___/\ Phillip Pi (Ant) / /\ /\ \ E-Mail: ph...@ea... or ph...@ap... | |. .| | \ _ / The Ant Farm: http://antfarm.home.dhs.org ( ) ICQ UIN: 2223658 |