Date: Thu, 18 Jun 2009 10:40:38 -0600 From: Nathan <nathan.stocks@gmail.com> To: Anton Shterenlikht <mexas@bristol.ac.uk> Cc: freebsd-gnome@freebsd.org Subject: Re: dbus, hal over xdmcp? Message-ID: <96c9d6a80906180940k7626e581g60c7f1a68006089a@mail.gmail.com> In-Reply-To: <20090618152536.GA24358@mech-cluster238.men.bris.ac.uk> References: <1240594738.58743.10.camel@shumai.marcuscom.com> <1241076847.28498.291.camel@shumai.marcuscom.com> <1241100519.1761.10.camel@balrog.2hip.net> <20090430142744.GA32844@mech-cluster238.men.bris.ac.uk> <1241301413.33649.110.camel@shumai.marcuscom.com> <20090616095729.GA98713@mech-cluster238.men.bris.ac.uk> <1245183702.71590.6.camel@shumai.marcuscom.com> <20090617101407.GB84905@mech-cluster238.men.bris.ac.uk> <96c9d6a80906170914i78c0d1fas5ffa77020ec28c36@mail.gmail.com> <20090618152536.GA24358@mech-cluster238.men.bris.ac.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Jun 18, 2009 at 9:25 AM, Anton Shterenlikht<mexas@bristol.ac.uk> wr=
ote:
> On Wed, Jun 17, 2009 at 10:14:03AM -0600, Nathan wrote:
>> On Wed, Jun 17, 2009 at 4:14 AM, Anton Shterenlikht<mexas@bristol.ac.uk>=
wrote:
>> > no, that doesn't work either.
>> > I wonder if anybody has actually successfully used dbus with XDMCP.
>> > I know it should work, but maybe nobody has tried, so perhaps there
>> > are some issues.
>> >
>> > I have a user group of about 20 people, all under the university firew=
all,
>> > so insecurity of XDMCP is not a major concern.
>> > I was thinking of having a powerful XDMCP server as an energy efficien=
t
>> > and easy to maintain model, since the desktops only need to have a goo=
d
>> > graphics card. If that is not working, then perhaps I have
>> > to switch to plain ssh tunneling, and have full X installation on all
>> > desktops.
>>
>> I don't know anything about dbus or hal, but we're using a FreeBSD 7.2
>> server that we just used to connect 150 thin clients (peak load of
>> about 100 concurrently connected right now) to it over XDMCP to use
>> gnome. =A0The biggest trick was finding the magic config line to
>> configure xdm with (since gdm's xdmcp doesn't work). =A0After that, our
>
> Could you please elaborate on this magic line?
>
> many thanks
>
> --
> Anton Shterenlikht
Absolutely. I preserved the exact procedures that we did to finally
make it work, so I'll just paste it in here for you. The "magic line"
that took us days to figure out is #2 below (apparently xdm doesn't
listen to any ipv4 ports/addresses without that line). Note that it
causes xdm to simply listen on all interfaces, from what I understand,
so you would want to modify it if you are not entirely on a secure
internal LAN. I used this procedure on FreeBSD 7.2-RELEASE-amd64.
1. Install xdm by entering cd /usr/ports/x11/xdm && make install
2. Add the following to the top of /usr/local/lib/X11/xdm/Xaccess:
LISTEN 0.0.0.0
3. ...and in the same file uncomment:
* #any host can get a login win=
dow
4. In /usr/local/lib/X11/xdm/Xsession comment out the line:
exec /usr/local/bin/xsm
5. And add this line right below it:
exec gnome-session
6. In /usr/local/lib/X11/xdm/xdm-config use ! to comment out the last
line so it looks like:
!DisplayManager.requestPort: 0
7. Edit /etc/ttys so that the ttyv8 line has on instead of off so it
looks like:
ttyv8 "/usr/local/bin/xdm -nodaemon" xterm on secure
8. Run kill -HUP 1 to make init reread /etc/ttys
~ Nathan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?96c9d6a80906180940k7626e581g60c7f1a68006089a>