From owner-freebsd-bugs Fri May 16 11:27:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA12176 for bugs-outgoing; Fri, 16 May 1997 11:27:21 -0700 (PDT) Received: from main.hq.cti.ru (main.hq.cti.ru [194.67.85.27]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA12159; Fri, 16 May 1997 11:26:53 -0700 (PDT) Received: from arc.hq.cti.ru (arc.hq.cti.ru [194.67.85.50]) by main.hq.cti.ru (8.8.5/8.8.5) with SMTP id WAA01950; Fri, 16 May 1997 22:26:42 +0400 (MSD) Date: Fri, 16 May 1997 22:26:41 +0400 (MSD) From: Dmitrij Tejblum To: "Jordan K. Hubbard" cc: jkh@hub.freebsd.org, freebsd-bugs@hub.freebsd.org Subject: Re: conf/3605 In-Reply-To: <199705161758.KAA10864@hub.freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, 16 May 1997, Jordan K. Hubbard wrote: > Yes, I'm also aware of issues like xdm leaving cacas around in /tmp > and refusing to start again if you terminate it abruptly, but > that's a bug in xdm which should be fixed there (it should check > to see if it's actually still running before heeding the lock file). Heh. I guess you use X from XiG, not from XFree86 ... ;-) > Clearing /tmp is evil and causes more problems than it solves - it's > been disabled on many of our machines since the very beginning and > should not be resurrected. May be, erase only /tmp/.X*-lock and /tmp/.X11-unix/* ? And, AFAIK, it never been disabled in distribution (and, therefore, *our* machines). Dima