From owner-freebsd-current@FreeBSD.ORG  Fri Mar 30 15:29:16 2012
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
	by hub.freebsd.org (Postfix) with ESMTP id 8A31A106564A
	for <freebsd-current@freebsd.org>; Fri, 30 Mar 2012 15:29:16 +0000 (UTC)
	(envelope-from luke@foolishgames.com)
Received: from stargazer.midnightbsd.org (cl-218.chi-02.us.sixxs.net
	[IPv6:2001:4978:f:d9::2])
	by mx1.freebsd.org (Postfix) with ESMTP id 245B18FC12
	for <freebsd-current@freebsd.org>; Fri, 30 Mar 2012 15:29:16 +0000 (UTC)
Received: from [10.68.200.80] (mobile-166-147-096-071.mycingular.net
	[166.147.96.71]) (authenticated bits=0)
	by stargazer.midnightbsd.org (8.14.5/8.14.5) with ESMTP id
	q2UFTBTs060912
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT);
	Fri, 30 Mar 2012 11:29:14 -0400 (EDT)
	(envelope-from luke@foolishgames.com)
X-Virus-Status: Clean
X-Virus-Scanned: clamav-milter 0.97.4 at stargazer.midnightbsd.org
X-Authentication-Warning: stargazer.midnightbsd.org: Host
	mobile-166-147-096-071.mycingular.net [166.147.96.71] claimed
	to be [10.68.200.80]
References: <4F746F1E.6090702@mail.zedat.fu-berlin.de>
	<4F74BCE8.2030802@vangyzen.net>
	<CACM2+-7Ahn6J=CTASe0g48+SD2vvLVd_hG3DRZmvO31QszG5Xw@mail.gmail.com>
	<20120330.151848.41706133.sthaug@nethelp.no>
	<CADLo839bF5Q+iZ-ExQi8VhpuAmxu+XhvZT7hVW35FCFq_V1huA@mail.gmail.com>
In-Reply-To: <CADLo839bF5Q+iZ-ExQi8VhpuAmxu+XhvZT7hVW35FCFq_V1huA@mail.gmail.com>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii
Message-Id: <ACCF8105-7367-4E6A-8AA6-CF3580AA9656@foolishgames.com>
X-Mailer: iPhone Mail (9B176)
From: Lucas Holt <luke@foolishgames.com>
Date: Fri, 30 Mar 2012 11:29:07 -0400
To: Chris Rees <utisoft@gmail.com>
Cc: "matt.thyer@gmail.com" <matt.thyer@gmail.com>,
	"ohartman@mail.zedat.fu-berlin.de" <ohartman@mail.zedat.fu-berlin.de>,
	"eric@vangyzen.net" <eric@vangyzen.net>,
	"sthaug@nethelp.no" <sthaug@nethelp.no>,
	"freebsd-current@freebsd.org" <freebsd-current@freebsd.org>
Subject: Re: Using TMPFS for /tmp and /var/run?
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Mar 2012 15:29:16 -0000

/tmp is used by eaccelerator for its cache. It's not required to persist but=
 does prevent the need to regenerate everything after a reboot.=20

Lucas Holt

On Mar 30, 2012, at 10:43 AM, Chris Rees <utisoft@gmail.com> wrote:

> On 30 Mar 2012 14:26, <sthaug@nethelp.no> wrote:
>>=20
>>>> However, if you always want to use tmpfs instead of stable storage,
>>> please do not.  Some people expect /tmp to be persistent.  This is why
>>> /etc/defaults/rc.conf has clear_tmp_enable=3D"NO".  Changing this would
> break
>>> the POLA.
>>>>=20
>>> This is a mistake.
>>>=20
>>> The default should be clear_tmp_enable=3D"YES"
>>> if only to uncover those broken configurations that expect /tmp to be
>>> persistent.
>>=20
>> If you want to break POLA and make a lot of people angry, sure.
>> Otherwise no.
>>=20
>=20
> I would very much like an example of where /tmp is expected to persist.
>=20
> Chris
> _______________________________________________
> freebsd-current@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"=