From owner-freebsd-questions Mon Feb 1 14:25:29 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA26491 for freebsd-questions-outgoing; Mon, 1 Feb 1999 14:25:29 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from mercury.webnology.com (mercury.webnology.com [209.155.51.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA26483 for ; Mon, 1 Feb 1999 14:25:26 -0800 (PST) (envelope-from jooji@webnology.com) Received: from localhost (jooji@localhost) by mercury.webnology.com (8.9.2/8.9.2) with SMTP id QAA07881; Mon, 1 Feb 1999 16:25:03 -0600 (CST) Date: Mon, 1 Feb 1999 16:25:03 -0600 (CST) From: "Jasper O'Malley" To: Evren Yurtesen cc: freebsd-questions@FreeBSD.ORG Subject: Re: why does /tmp world writable? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 1 Feb 1999, Evren Yurtesen wrote: > what if some non-root person crashes a process by filling up > /tmp directory? and when that proceses needs that directory > it will not be able to use it. Hopefully, you've got your machine paging you if/when your filesystems are filled up. If you like, as I suggested before, you can put /tmp on its own filesystem and apply (large) user quotas to it. That way, it takes a concerted effort to fill up /tmp, not one rogue user. But you really, really should keep the permissions on /tmp mode 1777. Cheers, Mick The Reverend Jasper P. O'Malley dotdot:jooji@webnology.com Systems Administrator ringring:asktheadmiral Webnology, LLC woowoo:http://www.webnology.com/~jooji To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message