From owner-freebsd-fs@FreeBSD.ORG Mon Apr 7 14:59:35 2014 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id EDB32A99 for ; Mon, 7 Apr 2014 14:59:35 +0000 (UTC) Received: from potato.growveg.org (potato.growveg.org [62.49.247.163]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id ABAF8A16 for ; Mon, 7 Apr 2014 14:59:35 +0000 (UTC) Received: from john by potato.growveg.org with local (Exim 4.82 (FreeBSD)) (envelope-from ) id 1WXB1H-0000Dc-Hq for freebsd-fs@freebsd.org; Mon, 07 Apr 2014 15:59:31 +0100 Date: Mon, 7 Apr 2014 15:59:31 +0100 From: John To: freebsd-fs@freebsd.org Subject: /boot/loader.conf or /etc/sysctl.conf ? zfs tunables Message-ID: <20140407145931.GC67619@potato.growveg.org> Mail-Followup-To: freebsd-fs@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.23 (2014-03-12) Sender: John X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: john@potato.growveg.org X-SA-Exim-Scanned: No (on potato.growveg.org); SAEximRunCond expanded to false X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: freebsd-fs@freebsd.org List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Apr 2014 14:59:36 -0000 Hello list, Is it safe for all zfs tunables to go in loader.conf? I see some are recommended to go in sysctl.conf. Well, not recommended, but quoted. Using /boot/loader.conf would, to me at least, be more systematic. Is there any harm in defining them all in there? If it is, it's not always obvious which goes where. thanks -- John