GNOME.org
 

Re: [gdm-list] multiseat

On 03/16/2011 09:40 AM, Brian Cameron wrote:


Yan:

On 03/16/11 10:31 AM, Yan Seiner wrote:
Is there a way to assign resources (keyboards, mice, cdrs, sound cards, etc)?
Right now I do it with a highly hacked up set of scripts and gdm 2.20 and 
it works - mostly.


Is Ubuntu now building with these patches to make the new GDM support
MultiSeat?

The new GDM supports the Init, PreSession, PostSession, and PostLogin
scripts just like the old GDM 2.20 did.  So, as long as you are using
these interfaces, it should work.

If you run into any issues getting this working in your setup, let us
know.  I'm sure others who might have issues would be interested to
hear how you get this working, especially if you find any gotchas.

Brian


Yan:
I was able to make minimal tweaks to gdm 2.20 to get multiseat working. I had a lot of practice, I've had a multseat since "backstreet ruby" hacks. It is very stable, you can hit CTRL+ALT+Backspace on either seat and it does not interfere with the other. One thing I did have to do is make sure Compiz was not running for any user logging in. My son and I play BZFlag side by side on the same box with 2x Nvidia 8400GS, it works great.. Both seats get about 150-170fps, OpenGL is working really well for the last ~3 years. 

Brian:
Thank you for the config info. I will track down what is in the Ubuntu packages, I will report back, and do my own patches if necessary. 

Thanks,
Scott






On Wed, March 16, 2011 8:25 am, Brian Cameron wrote:


MultiSeat is not supported by GDM 2.21 or later, unless GDM is built
with the patch in this bug:

    https://bugzilla.gnome.org/show_bug.cgi?id=536355

And if ConsoleKit is built with the patch in this bug:

    https://bugs.freedesktop.org/show_bug.cgi?id=19333

I am not sure if Ubuntu does this already or not.  If they do, you
configure this via /etc/ConsoleKit interfaces and not via the
GDM configuration file anymore.  If your system has an
/etc/ConsoleKit/seats.d directory, then this feature should work
on your system.

Here are some examples which show how you can configure it via the new
interfaces:

       Example 1: To start the ConsoleKit daemon

       example% console-kit-daemon

       Example 2: To configure ConsoleKit to not start a seat

       To disable a seat, the administrator can set Hidden=true  in
       the  .seat file. Edit the 00-primary.seat file as follows to
       disable the default primary seat which normally runs on  the
       system console.

       For example, disabling the primary seat on  the  console  is
       useful  if  the  administrator wishes to run GDM in headless
       mode. This can be useful if the administrator wants  GDM  to
       accept  XDMCP  remote displays but the server does not actu-
       ally have a console.

       [Seat Entry]
       Version=1.0
       Name=Primary seat
       ID=StaticSeat1
       Description=start one static local display at :0
       Hidden=true
       Devices=
       Sessions=Local;

       Example 3: To configure ConsoleKit to  start  multiple  ses-
       sions on a single seat

       To start two local displays: DISPLAY ":0" on vt7 and DISPLAY
       ":1" on "vt8", edit the 00-primary.seat file as follows:

       [Seat Entry]
       Version=1.0
       Name=Primary seat
       Description=start static displays :0 on vt7 and :1 on vt8
       Hidden=false
       Devices=
       Sessions=Local;Local2;

       Then,      in      addition      to       the       original
       /etc/ConsoleKit/sessions.d/Local.session  file, add the fol-
       lowing /etc/ConsoleKit/sessions.d/Local2.session file:

       [Session Entry]
       Name=Local
       Type=LoginWindow
       Description=Local Login Screen
       DisplayTemplate=Local

       [Local]
       display=:1
       vt=vt8

       Example 4: To configure ConsoleKit to start multiple seat

       To start two seats: a local session on  DISPLAY  ":0"  using
       "vt7" and another seat using a VNC session on DISPLAY ":64",
       add a file /etc/ConsoleKit/seats.d/01-vnc.seat as follows:

       [Seat Entry]
       Version=1.0
       Name=VNC seat
       Description=start one VNC display on :64
       Hidden=false
       Devices=
       Sessions=LocalVNC;

       Add the /etc/ConsoleKit/sessions.d/LocalVNC.session file  as
       follows:

       [Session Entry]
       Name=LocalVNC
       Type=LoginWindow
       Description=Connect to local VNC server running on same machine
       DisplayTemplate=LocalVNC

       [LocalVNC]
       display=:64

       Finally, add the /etc/ConsoleKit/displays.d/LocalVNC.display
       file as follows:

       [Display]
       Type=X11

       [X11]
       Exec=/usr/X11/bin/Xvnc $display -auth $auth -query localhost

On Solaris, we update the console-kit-daemon manpage with these
examples to help people figure out how to do this.

Brian


On 03/16/11 09:57 AM, Scott Serr wrote:

I'm doing some preliminary testing of Ubuntu 11.04 (Alpha3+Updates) to
replace my aging Ubuntu 8.04 Multiseat setup. Multiseat was do-able in 
gdm 2.20.5, but I would probably call it a hack.
Is the current state of gdm 2.32.0 that it won't support multiseat? Or 
is it just that it's not some how a menu driven configuration option?

I've read some posts for 2.32 that there are patches for multiseat.

With or without the patches, where would I find configuration
information?  I'm familiar with gdm.conf hacks to add:

[servers]
0=Seat0
1=Seat1

etc...

But things are very different now.

Thanks for any help.
-Scott
____________________________________
[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]