From owner-freebsd-gnome@FreeBSD.ORG Fri Jun 19 09:38:43 2009 Return-Path: Delivered-To: freebsd-gnome@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C67F11065673 for ; Fri, 19 Jun 2009 09:38:43 +0000 (UTC) (envelope-from mexas@bristol.ac.uk) Received: from dirg.bris.ac.uk (dirg.bris.ac.uk [137.222.10.102]) by mx1.freebsd.org (Postfix) with ESMTP id 7A7308FC15 for ; Fri, 19 Jun 2009 09:38:43 +0000 (UTC) (envelope-from mexas@bristol.ac.uk) Received: from seis.bris.ac.uk ([137.222.10.93]) by dirg.bris.ac.uk with esmtp (Exim 4.69) (envelope-from ) id 1MHaYQ-0004Px-M8; Fri, 19 Jun 2009 10:38:41 +0100 Received: from mech-cluster238.men.bris.ac.uk ([137.222.187.238]) by seis.bris.ac.uk with esmtp (Exim 4.67) (envelope-from ) id 1MHaYP-00072t-Or; Fri, 19 Jun 2009 10:38:38 +0100 Received: from mech-cluster238.men.bris.ac.uk (localhost.men.bris.ac.uk [127.0.0.1]) by mech-cluster238.men.bris.ac.uk (8.14.3/8.14.3) with ESMTP id n5J9cahj082542; Fri, 19 Jun 2009 10:38:36 +0100 (BST) (envelope-from mexas@bristol.ac.uk) Received: (from mexas@localhost) by mech-cluster238.men.bris.ac.uk (8.14.3/8.14.3/Submit) id n5J9ca3Y082537; Fri, 19 Jun 2009 10:38:36 +0100 (BST) (envelope-from mexas@bristol.ac.uk) X-Authentication-Warning: mech-cluster238.men.bris.ac.uk: mexas set sender to mexas@bristol.ac.uk using -f Date: Fri, 19 Jun 2009 10:38:36 +0100 From: Anton Shterenlikht To: Nathan Message-ID: <20090619093836.GA72981@mech-cluster238.men.bris.ac.uk> References: <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> <96c9d6a80906180940k7626e581g60c7f1a68006089a@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <96c9d6a80906180940k7626e581g60c7f1a68006089a@mail.gmail.com> User-Agent: Mutt/1.5.19 (2009-01-05) X-Spam-Score: -1.4 X-Spam-Level: - Cc: freebsd-gnome@freebsd.org Subject: Re: dbus, hal over xdmcp? X-BeenThere: freebsd-gnome@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GNOME for FreeBSD -- porting and maintaining List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Jun 2009 09:38:44 -0000 On Thu, Jun 18, 2009 at 10:40:38AM -0600, Nathan wrote: > On Thu, Jun 18, 2009 at 9:25 AM, Anton Shterenlikht wrote: > > On Wed, Jun 17, 2009 at 10:14:03AM -0600, Nathan wrote: > >> On Wed, Jun 17, 2009 at 4:14 AM, Anton Shterenlikht 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 firewall, > >> > so insecurity of XDMCP is not a major concern. > >> > I was thinking of having a powerful XDMCP server as an energy efficient > >> > and easy to maintain model, since the desktops only need to have a good > >> > 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.  The biggest trick was finding the magic config line to > >> configure xdm with (since gdm's xdmcp doesn't work).  After 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 I've got the ip address of the XDMCP server > 3. ...and in the same file uncomment: > > * #any host can get a login window yes, I've got this > 4. In /usr/local/lib/X11/xdm/Xsession comment out the line: > > exec /usr/local/bin/xsm I've got this in, but it's never executed because I use $HOME/.xsession > 5. And add this line right below it: > > exec gnome-session I see. So your users don't have $HOME/.xsession files? I guess I could've put /usr/local/bin/mwm here instead of in $HOME/.xsession > 6. In /usr/local/lib/X11/xdm/xdm-config use ! to comment out the last > line so it looks like: > > !DisplayManager.requestPort: 0 yes, it took me a while to figure this out. The problem is that any upgrade of xdm overwtites this back to the default. > 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 I start xdm manually. I was under the impression the above line wouldn't work on a headless box. > 8. Run kill -HUP 1 to make init reread /etc/ttys yes, sure Few more questions, if you please: What architecture are your XDMCP server and the desktops? Do the users start X with -query ? many thanks anton -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 928 8233 Fax: +44 (0)117 929 4423