From owner-freebsd-security Tue Sep 4 4: 5:48 2001 Delivered-To: freebsd-security@freebsd.org Received: from bsd.ist-ffo.de (bsd.ist-ffo.de [192.124.253.37]) by hub.freebsd.org (Postfix) with ESMTP id 7256E37B41B for ; Tue, 4 Sep 2001 04:05:41 -0700 (PDT) Received: (from griesche@localhost) by bsd.ist-ffo.de (8.11.1/8.11.1) id f84B5dq06623; Tue, 4 Sep 2001 13:05:39 +0200 (CEST) Date: Tue, 4 Sep 2001 13:05:39 +0200 (CEST) From: Joachim Griesche Message-Id: <200109041105.f84B5dq06623@bsd.ist-ffo.de> To: freebsd-security@freebsd.org Subject: Re: Good practice for /tmp Cc: griesche@bsd.ist-ffo.de Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hello! Although putting /tmp on its own partition is helpful, I prefer not to symlink /var/tmp to /tmp because /tmp and /var/tmp are handled in a different manner by most systems: While /tmp is cleared at boot time, /var/tmp is not (see the file /etc/rc and the comments where), preserving recovery files. If /tmp is not on its own partition, I create /usr/tmp and symlink /tmp to /usr/tmp in order to avoid filling of /. With best regards Joachim Griesche System administrator Institut fuer Solartechnologien GmbH Frankfurt (Oder), Germany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message