From owner-freebsd-questions Fri Dec 8 14:12: 2 2000 From owner-freebsd-questions@FreeBSD.ORG Fri Dec 8 14:11:59 2000 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from guru.mired.org (okc-65-26-235-186.mmcable.com [65.26.235.186]) by hub.freebsd.org (Postfix) with SMTP id E0A5B37B400 for ; Fri, 8 Dec 2000 14:11:58 -0800 (PST) Received: (qmail 90747 invoked by uid 100); 8 Dec 2000 22:11:58 -0000 From: Mike Meyer MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14897.23726.262612.101525@guru.mired.org> Date: Fri, 8 Dec 2000 16:11:58 -0600 (CST) To: Christopher Farley Cc: questions@freebsd.org Subject: Re: Weird /tmp issues In-Reply-To: <95144528@toto.iv> X-Mailer: VM 6.75 under 21.1 (patch 10) "Capitol Reef" XEmacs Lucid X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`;h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Christopher Farley types: > Corey Brune (brune@sdf.lonestar.org) wrote: > > > /tmp should be chmod'ed with 1777 for the sticky bit turned on. I am *think* > > the perms affect X. Try it out and see if this corrects the problem. > Strange, but it doesn't! The only thing that restores X11 functionality > is copying the old tmp directory back. > > This doesn't make any sense to me -- if /tmp were swap, wouldn't it get > cleared at each reboot? Isn't that a common configuration? 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? 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. http://www.mired.org/home/mwm/ Independent WWW/Unix/FreeBSD consultant, email for more information. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message