Date: Sun, 26 Jun 2005 22:53:19 +1000 From: duckeo <duckeo@gmail.com> To: Garrett Cooper <youshi10@u.washington.edu> Cc: freebsd-questions@freebsd.org Subject: Re: Xvnc + inetd Message-ID: <894159540506260553650b78c@mail.gmail.com> In-Reply-To: <42BEA24B.7060109@u.washington.edu> References: <89415954050626001752c3c470@mail.gmail.com> <42BE9CDB.5040502@u.washington.edu> <89415954050626052730dc30d4@mail.gmail.com> <894159540506260530596e4be9@mail.gmail.com> <42BEA24B.7060109@u.washington.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On 6/26/05, Garrett Cooper <youshi10@u.washington.edu> wrote: > duckeo wrote: >=20 > >On 6/26/05, duckeo <duckeo@gmail.com> wrote: > > > > > >>Because isn't VNC far more efficient? I've read X is only really > >>useful locally, also because VNC is more common a client on Windows > >>machines (as in already installed). > >> > >> > I'm not sure if that's true or not. I've talked to various people > who've advocated both angles, but it appears that X forwarding is > (arguably) more secure. I don't know if this is the case or not, and I > also don't know if they were referring to not SSH port forwarded > connections as opposed to a non-localhost-only based server. > But I do know that running multiple separate X sessions as opposed > to X port forwarding is overall less efficient if you're dealing with a > large number of users accessing one host. This is true because VNC-in > various forms-has a tendency to eat up some userspace memory (I think > around 5-8Mb per instance), in addition to the actual X session > allocated memory that it's associated with. That's just a thought to > consider when comparing the two. > -Garrett I'll take that into consideration as the usercount starts to increase on the box, at the moment it will be mostly network oriented IT staff needing access to utilities. The main concern is access to X from Windows machines, and VNC still seems to be the easiest method (we also have things like activeX capabale VNC clients we like to use for remote access).
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?894159540506260553650b78c>