Jonathan Underwood wrote:
On 22/01/2008, Les Mikesell <lesmikesell@xxxxxxxxx> wrote:
Jonathan Underwood wrote:
On 22/01/2008, Les Mikesell <lesmikesell@xxxxxxxxx> wrote:
And to confuse things a bit more, the vncts package that starts new
sessions on demand through xinetd would also conflict in a different way.
Huh? What's this vncts package? This sounds interesting.
It's a setup to let xinetd start instances of Xvnc that do localhost
XDMCP logins for each connection. Several ports are configured to give
a choice of screen size and color depth. I've only used it on the
k12ltsp distribution but I think it is a stock fedora package. K12ltsp
is configured by default to accept XDMCP logins from thin clients and
you might have to tweak this on a stock fedora.
Ah, ok, I thought perhaps it was a package in the Fedora repo. Shame.
I thought it was - just not installed by default, but it looks like the
one I have is from the vnc-ltsp-config package.
I did post a very simple recipe for doing exactly this (vnc sessions
started with xinetd) on this list a few weeks ago actually - it really
does seem the simplest solution to me. (Subject of the message was
"VNC and a full login Gnome session with GDM "). Would be nice if this
was actully working out-of-the-box in a standard install, IMO.
It's one of several reasons that I always install k12ltsp even if I
don't plan on booting thin clients. K12ltsp isn't a different
distribution in the usual sense - it is a fedora/centos (depending on
the version) respin with the current updates applied at the time of its
release and some extra packages and scripts included - one of which
makes vnc sessions-on-demand come up working by default.
--
Les Mikesell
lesmikesell@xxxxxxxxx
