From owner-freebsd-current@FreeBSD.ORG Wed Apr 8 00:27:50 2009 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 08566106566C; Wed, 8 Apr 2009 00:27:50 +0000 (UTC) (envelope-from marcus@FreeBSD.org) Received: from creme-brulee.marcuscom.com (marcuscom-pt.tunnel.tserv1.fmt.ipv6.he.net [IPv6:2001:470:1f00:ffff::1279]) by mx1.freebsd.org (Postfix) with ESMTP id A4DA98FC17; Wed, 8 Apr 2009 00:27:49 +0000 (UTC) (envelope-from marcus@FreeBSD.org) Received: from [IPv6:2001:470:1f00:2464::4] (shumai.marcuscom.com [IPv6:2001:470:1f00:2464::4]) by creme-brulee.marcuscom.com (8.14.3/8.14.3) with ESMTP id n380SDGM028577; Tue, 7 Apr 2009 20:28:13 -0400 (EDT) (envelope-from marcus@FreeBSD.org) From: Joe Marcus Clarke To: Tim Kientzle In-Reply-To: <92cd2ff70904071653r4bf3b381lf5de220b2e280c0c@mail.gmail.com> References: <934e1d760904061455o4736d643o1d07e3292192d94c@mail.gmail.com> <1239077210.1908.39.camel@balrog.2hip.net> <49DAD429.6090309@freebsd.org> <1239078081.1908.41.camel@balrog.2hip.net> <49DAE987.7090802@freebsd.org> <1239086408.35025.59.camel@shumai.marcuscom.com> <20090407185915.GY31409@albert.catwhisker.org> <49DBA371.3080804@freebsd.org> <92cd2ff70904071637h362da63ua13c1f8eca6fc616@mail.gmail.com> <1239147806.98664.12.camel@shumai.marcuscom.com> <92cd2ff70904071653r4bf3b381lf5de220b2e280c0c@mail.gmail.com> Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-S70c94Nmoyk0nw29QBob" Organization: FreeBSD, Inc. Date: Tue, 07 Apr 2009 20:27:49 -0400 Message-Id: <1239150469.98664.18.camel@shumai.marcuscom.com> Mime-Version: 1.0 X-Mailer: Evolution 2.24.5 FreeBSD GNOME Team Port X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,NO_RELAYS autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on creme-brulee.marcuscom.com Cc: current@FreeBSD.org, Robert Noland Subject: Re: Hal and KDM breakage (was Re: KDE4 and input events stalled) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Apr 2009 00:27:50 -0000 --=-S70c94Nmoyk0nw29QBob Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Tue, 2009-04-07 at 16:53 -0700, Tim Kientzle wrote: > On Tue, Apr 7, 2009 at 4:43 PM, Joe Marcus Clarke > wrote: > =20 > =20 > It's not a question of what hal is doing, but rather how > console-kit > works (and hald depends on console-kit-daemon). It needs to > be able to > monitor each of the active vtys... >=20 > This is the part of the picture I'm still missing. *Why* does > hald (via console-kit) care about tracking active vtys? > (I presume hald actually doesn't care but that some client > of hald needs this information.... ???) ConsoleKit monitors the vtys for active changes so it can provide consumers such as hal and PolicyKit information about active sessions. In particular, hal uses CK to determine if a user is currently logged in on the console, and if so, allows that user to mount certain volumes that would otherwise not be allowed. >=20 >=20 > .... Bland did some work to correct this in -CURRENT, but it > won't work on other versions. It was just easier to leave the > hack in > place. > =20 > If this could be universally fixed in all supported versions > of FreeBSD, > then I would be happy to remove the hacks. >=20 > I'm still curious whether it's feasible to just not monitor the vtys. Sure, you can try it. Especially if you're not using GNOME, this might be fine. Just remove the hacks from hald's rc.d script. Joe >=20 --=20 Joe Marcus Clarke FreeBSD GNOME Team :: gnome@FreeBSD.org FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome --=-S70c94Nmoyk0nw29QBob Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEABECAAYFAknb74MACgkQb2iPiv4Uz4cfpgCgsMD/5oFjghbpVFQ0jr8qNast +DUAniY5q4xdIL8z3ndKGpTpeRDuW2nd =072A -----END PGP SIGNATURE----- --=-S70c94Nmoyk0nw29QBob--