Date: Fri, 30 Mar 2012 23:21:05 +1030 From: Matt Thyer <matt.thyer@gmail.com> To: Eric van Gyzen <eric@vangyzen.net> Cc: "O. Hartmann" <ohartman@mail.zedat.fu-berlin.de>, FreeBSD current <freebsd-current@freebsd.org> Subject: Re: Using TMPFS for /tmp and /var/run? Message-ID: <CACM2%2B-7Ahn6J=CTASe0g48%2BSD2vvLVd_hG3DRZmvO31QszG5Xw@mail.gmail.com> In-Reply-To: <4F74BCE8.2030802@vangyzen.net> References: <4F746F1E.6090702@mail.zedat.fu-berlin.de> <4F74BCE8.2030802@vangyzen.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mar 30, 2012 6:22 AM, "Eric van Gyzen" <eric@vangyzen.net> wrote: > 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="NO". Changing this would break the POLA. > This is a mistake. The default should be clear_tmp_enable="YES" if only to uncover those broken configurations that expect /tmp to be persistent. I was going to say "At least on -CURRENT" but in reality it should be the default on -RELEASE too when it's clearly a bug to expect /tmp to be persistent.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CACM2%2B-7Ahn6J=CTASe0g48%2BSD2vvLVd_hG3DRZmvO31QszG5Xw>