From owner-freebsd-current@FreeBSD.ORG Thu Mar 29 14:18:13 2012 Return-Path: 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 ED1F71065672 for ; Thu, 29 Mar 2012 14:18:13 +0000 (UTC) (envelope-from ohartman@mail.zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) by mx1.freebsd.org (Postfix) with ESMTP id A385A8FC16 for ; Thu, 29 Mar 2012 14:18:13 +0000 (UTC) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost1.zedat.fu-berlin.de (Exim 4.69) for freebsd-current@freebsd.org with esmtp (envelope-from ) id <1SDGB2-0003Jg-J1>; Thu, 29 Mar 2012 16:18:12 +0200 Received: from telesto.geoinf.fu-berlin.de ([130.133.86.198]) by inpost2.zedat.fu-berlin.de (Exim 4.69) for freebsd-current@freebsd.org with esmtpsa (envelope-from ) id <1SDGB2-0006Dz-F4>; Thu, 29 Mar 2012 16:18:12 +0200 Message-ID: <4F746F1E.6090702@mail.zedat.fu-berlin.de> Date: Thu, 29 Mar 2012 16:18:06 +0200 From: "O. Hartmann" User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:10.0.3) Gecko/20120314 Thunderbird/10.0.3 MIME-Version: 1.0 To: Current FreeBSD X-Enigmail-Version: 1.4 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig0D51AADCEDC563595301A38A" X-Originating-IP: 130.133.86.198 X-Mailman-Approved-At: Thu, 29 Mar 2012 15:49:22 +0000 Subject: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Mar 2012 14:18:14 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig0D51AADCEDC563595301A38A Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: quoted-printable I was wondering if there are some objections using TMPFS for /tmp and /var/run. I figured out some problems with some rc.d scripts when using TMPFS for /var/run, samba and OpenLDAP do store some informations like PID in a subfolder of their own in /var/run, but the rc.d scripts are not checking properly the existence of the appropritae folder (unlike "dbus" and "hald", they check properly!). I already submitted two PRs, but for SAMBA, my "hack" is trivial and obviously to clumsy, so it should be check properly. My question is whether there are objections using TMPFS for bot /tmp/ and /var/run/ at this stage on FreeBSD 10.0-CURRENT/amd64? Regards, Oliver --------------enig0D51AADCEDC563595301A38A Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iQEcBAEBAgAGBQJPdG8kAAoJEOgBcD7A/5N8h2oH/AlVcbr8LPzzluGc0OT0p1tl LXXPKrTwN1KmnyfEwMMa0V4UtaGQHlIlzmaesakuBvMrxVx4yaV9Zc2LA3Yld2cA eT0z0VcnOcAF3ghTCC9AWst0ANxt4FvW7jE2xvry3g8QEHLGxWm8yVHDWqTZ8DMp NXjfzyrDl+5T9kikOEWiQH2nxBrgKyIgVDUq5idoovlAcamOa8Agsafsgs9sLEnj sTVijd4dbHh8L9JSqzi/yYDDV20p0PT0F5QfzgQ4R1eixMBlOdjUtqS9TclYxlNB UtUS+sM2eKeNDP4EC85FvO6QF6mw+AGXkf+nE/uO9nHuAw/u6FKuPU0bhzmaRg8= =ER8a -----END PGP SIGNATURE----- --------------enig0D51AADCEDC563595301A38A--