From owner-freebsd-questions@FreeBSD.ORG Fri Apr 24 17:28:22 2015 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 39B7D236 for ; Fri, 24 Apr 2015 17:28:22 +0000 (UTC) Received: from mail-wg0-x22c.google.com (mail-wg0-x22c.google.com [IPv6:2a00:1450:400c:c00::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C135D19D3 for ; Fri, 24 Apr 2015 17:28:21 +0000 (UTC) Received: by wgin8 with SMTP id n8so57751152wgi.0 for ; Fri, 24 Apr 2015 10:28:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=date:from:to:subject:message-id:in-reply-to:references:mime-version :content-type:content-transfer-encoding; bh=Me1Lj6kuOSEWCNAmmIm8F60xz9nCorRK/Ck/5KKbXEY=; b=qQiKkytIymm+P9xevk2FElPJqwcUVTMWM3ofLfJSqM3oXF1FAcSLtf5qW7Bvae7mRg 6cSENTEPharsvoac0GcyCBrpVXhpz+KmFUQoJamdch6KOFoDkVn+jddaXCCF3AzrPoDM eXsfVwkRfEQLIoaqmUD+3g6eoNGEp2G/siccch7gQxXHm4QXvHBOGLTJ4gH9ptofALkr bF7hYLIOzbHCozHAmM4IYC+y52uHK6AOpBbpoUlR/wo9QM1hiQfOIChwUsRpCxRwQ29k TiBQzlxE4KC2jM7iYHeVNSed4AoWto61rC2f6zofYFfD3c2jaryL3gjXHxg/i43jLvqk kvfA== X-Received: by 10.180.99.166 with SMTP id er6mr194218wib.58.1429896499969; Fri, 24 Apr 2015 10:28:19 -0700 (PDT) Received: from gumby.homeunix.com (5ec3c570.skybroadband.com. [94.195.197.112]) by mx.google.com with ESMTPSA id ha4sm5830wib.0.2015.04.24.10.28.18 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 24 Apr 2015 10:28:19 -0700 (PDT) Date: Fri, 24 Apr 2015 18:28:15 +0100 From: RW To: freebsd-questions@freebsd.org Subject: Re: ufs snapshot help Message-ID: <20150424182815.33b1c95d@gumby.homeunix.com> In-Reply-To: <14591.128.135.70.2.1429886972.squirrel@cosmo.uchicago.edu> References: <65468.128.135.70.2.1429815636.squirrel@cosmo.uchicago.edu> <20150424123823.1f02c665@gumby.homeunix.com> <14591.128.135.70.2.1429886972.squirrel@cosmo.uchicago.edu> X-Mailer: Claws Mail 3.11.1 (GTK+ 2.24.25; amd64-portbld-freebsd10.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Apr 2015 17:28:22 -0000 On Fri, 24 Apr 2015 09:49:32 -0500 (CDT) Valeri Galtsev wrote: > > On Fri, April 24, 2015 6:38 am, RW wrote: > > On Thu, 23 Apr 2015 14:00:36 -0500 (CDT) > > Valeri Galtsev wrote: > > > >> > > > >> Once (a while ago) I noticed Linuxes have started in addition > >> to /tmp using /var/tmp, > > > > FreeBSD has always had /var/tmp. It's perfectly sensible, file > > in /tmp don't need to survive a reboot, those in /var/tmp do. > > Functionality wise, yes. Security/robustness wise, no. Well, one can > have both by creation of yet another partition and mounting it > as /var/tmp. Then regular user will not be able to just fill up /var > (through /var/tmp) thus stopping logs being incremented, preventing > daemons being started (the ones that need to write their PID > into /var/run) etc. But FreeBSD has /var/tmp, it's had it since the beginning, it's certainly not a Linuxism. I don't recall it ever being a separate partition in a default install, or the handbook suggesting that it might be one. If Linux is brain-dead for having it in /var then FreeBSD is too. FreeBSD, by default, reserves 8% of space for root so filling up /var with user files doesn't stop most daemon from starting and most are started at boot anyway. Filling-up /tmp or /var/tmp can create worse problems for daemons than filling-up /var. FWIW back in the 1970's the original reason for having a /usr/tmp was to keep user files out of /tmp altogether.