Date: Mon, 24 Jan 2011 22:46:58 +0200 From: David Naylor <naylor.b.david@gmail.com> To: FreeBSD <freebsd-questions@freebsd.org> Subject: Re: putting "/tmp" to memory Message-ID: <201101242247.01839.naylor.b.david@gmail.com> In-Reply-To: <20110124075205.4632d037@scorpio> References: <12db3210cd2.-2509072410058136592.-3952788888916668261@zoho.com> <20110124121821.107c2061@gumby.homeunix.com> <20110124075205.4632d037@scorpio>
next in thread | previous in thread | raw e-mail | index | archive | help
--nextPart1481622.SUHsuLPYD3 Content-Type: Text/Plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable On Monday 24 January 2011 14:52:05 Jerry wrote: > On Mon, 24 Jan 2011 12:18:21 +0000 >=20 > RW <rwmaillists@googlemail.com> articulated: > > I have > >=20 > > tmpfs /tmp tmpfs rw,size=3D4280000000 > >=20 > > I would suggest you don't use tmpmfs=3D"YES" in rc.conf unless you are > > being very conservative with a production server. tmpfs is nominally > > experimental, but it seems to be very stable, and it's much more > > memory efficient than md devices. >=20 > On a FreeBSD 8.2-PRERELEASE, I have the following: >=20 > cat /etc/fstab | grep -i "tmpfs" > tmpfs /tmp tmpfs rw,mode=3D01777 0 0 >=20 > It works very well and I have not noticed any problems whatsoever. I have noticed that editors/openoffice.org-3 will fail to build if /tmp is= =20 tmpfs. Other than that it has been stable for me. =20 --nextPart1481622.SUHsuLPYD3 Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (FreeBSD) iEYEABECAAYFAk095UUACgkQUaaFgP9pFrIoAQCeI6FyEvNJPf0mB3OyooUPmuH6 4+8An1Mg/ueCfDpBB56PNyHwEvLyUxGg =Eu77 -----END PGP SIGNATURE----- --nextPart1481622.SUHsuLPYD3--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201101242247.01839.naylor.b.david>