From owner-freebsd-questions Wed Feb 14 6:50: 4 2001 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 DD64037B503 for ; Wed, 14 Feb 2001 06:49:58 -0800 (PST) Received: (qmail 2668 invoked by uid 100); 14 Feb 2001 14:49:58 -0000 From: Mike Meyer MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14986.39702.161235.993817@guru.mired.org> Date: Wed, 14 Feb 2001 08:49:58 -0600 To: "NetAdmin - FoxChat.Net" Cc: questions@freebsd.org Subject: Re: /tmp In-Reply-To: <33140629@toto.iv> X-Mailer: VM 6.89 under 21.1 (patch 14) "Cuyahoga Valley" 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 NetAdmin - FoxChat.Net types: > I'm running 3.5-Stable and every time I add a user via /stand/sysinstall > I get something similar to the following - "can not write to /tmp - To > many links" Is it safe to rm -rf /tmp? Is there a way to clean up the > /tmp or links? I've looked all over the help files in www.defcon1.org > and can't seem to find anything other than a patch for 4.2 for a > vulnerability in the /tmp. You need to have a /tmp. However, it's not really safe to remove everything in it while you're running multiuser. You can safely go into it and remove everything older than your last reboot by hand. To clean all of it out safely, you should be single user. This is one reason for wanting to run an mfs or md based /tmp. http://www.mired.org/home/mwm/ Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message