From owner-freebsd-questions@FreeBSD.ORG Mon Feb 13 15:30:07 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 262B616A420 for ; Mon, 13 Feb 2006 15:30:07 +0000 (GMT) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: from mail5.sea5.speakeasy.net (mail5.sea5.speakeasy.net [69.17.117.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9B63343D66 for ; Mon, 13 Feb 2006 15:30:04 +0000 (GMT) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: (qmail 11431 invoked from network); 13 Feb 2006 15:30:03 -0000 Received: from dsl092-078-145.bos1.dsl.speakeasy.net (HELO be-well.ilk.org) ([66.92.78.145]) (envelope-sender ) by mail5.sea5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 13 Feb 2006 15:30:03 -0000 Received: by be-well.ilk.org (Postfix, from userid 1147) id 7619528439; Mon, 13 Feb 2006 10:30:02 -0500 (EST) Sender: lowell@be-well.ilk.org To: Bob Perry References: <43DC4330.6080607@gti.net> <441wypu812.fsf@be-well.ilk.org> <43DE445A.3040904@gti.net> <44ek2p5ppq.fsf@be-well.ilk.org> <43EF6DF5.3090709@gti.net> From: Lowell Gilbert Date: 13 Feb 2006 10:30:02 -0500 In-Reply-To: <43EF6DF5.3090709@gti.net> Message-ID: <44irrjl1j9.fsf@be-well.ilk.org> Lines: 17 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: freebsd-questions@freebsd.org Subject: Re: Unable to Startx Following Upgrade--Error in Locking Authority File X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Feb 2006 15:30:07 -0000 Bob Perry writes: > Not sure if I updated folks on this but the problem persists. (E-mail > problems). I've since requested assistance from the gnome and x11 > mailing list since the problem started following recent upgrades to > those ports. The base system has added some "/tmp"-cleaning at boot time, specifically to clear out X-related directories. Updating your system to (for example) 6-STABLE may make things work automatically. Alternatively, you could turn on the old /tmp cleaning, which will just wipe the whole directory. If you have a single-user system, the security risks aren't really an issue. Or you could use a memory disk for /tmp. That will (obviously) clear your whole /tmp automatically on a reboot. I do that on my desktops, by setting the tmpmfs and tmpsize variables in rc.conf(5).