From owner-freebsd-questions Fri Dec 8 14:53:31 2000 From owner-freebsd-questions@FreeBSD.ORG Fri Dec 8 14:53:29 2000 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from kraeusen.nbrewer.com (unknown [208.42.68.65]) by hub.freebsd.org (Postfix) with ESMTP id CE42537B400 for ; Fri, 8 Dec 2000 14:53:28 -0800 (PST) Received: by kraeusen.nbrewer.com (Postfix, from userid 1001) id BAEF817434; Fri, 8 Dec 2000 16:53:27 -0600 (CST) Date: Fri, 8 Dec 2000 16:43:27 -0600 From: Christopher Farley To: Mike Meyer Subject: Re: Weird /tmp issues Message-ID: <20001208164327.A541@northernbrewer.com> References: <95144528@toto.iv> <14897.23726.262612.101525@guru.mired.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <14897.23726.262612.101525@guru.mired.org>; from mwm@mired.org on Fri, Dec 08, 2000 at 04:11:58PM -0600 Resent-From: chris@northernbrewer.com Resent-Date: Fri, 8 Dec 2000 16:53:27 -0600 Resent-To: freebsd-questions@freebsd.org Resent-Message-Id: <20001208225327.BAEF817434@kraeusen.nbrewer.com> Resent-Sender: chris@nbrewer.com Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Meyer (mwm@mired.org) wrote: > Christopher Farley types: > I run tmp on swap (via mfs), and it works fine. However, it gets > recreated *on reboots*. I didn't see you talk about a reboot - have > you tried that? Oh yes. And even after a reboot, /tmp is filled with all kinds of crap, namely those unix domain sockets and lockfiles created by X. > X creates lock files and unix domain sockets in /tmp. If you don't > want to reboot with the new /tmp in place, you might try moving > /tmp.old/.X* to /tmp. The sockets have been causing trouble. When I tried to mv /tmp /usr/tmp, I get an "Operation not permitted" on every socket. I have not tried to move the sockets separately. I can mv /tmp all over the root filesystem, of course; just not to any other filesystems. (I assume mv renames if the target filesystem is the same as the source, and copies the files otherwise.) Those sockets remain even after a reboot; even if I don'r run X. Is this normal? I would think if you shutdown X, it would remove all its lockfiles and sockets. It seems as if X requires those sockets to run, because if I move /tmp, my display and keyboard both fail until a reboot. I searched deja.com regarding this issue, and found a message from someone who said "I like to move /tmp to a diferent filesystem before X has a chance to establish sockets there." -- Christopher Farley Northern Brewer / 1150 Grand Avenue / St. Paul, MN 55105 www.northernbrewer.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message