From owner-freebsd-questions@FreeBSD.ORG Wed May 9 08:15:59 2012 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 825B5106566C for ; Wed, 9 May 2012 08:15:59 +0000 (UTC) (envelope-from peter@vereshagin.org) Received: from mx1.skyriver.ru (ns1.skyriver.ru [89.108.118.221]) by mx1.freebsd.org (Postfix) with ESMTP id 37AD78FC0A for ; Wed, 9 May 2012 08:15:59 +0000 (UTC) Received: from localhost (h-234-182.a189.priv.bahnhof.se [81.170.234.182]) by mx1.skyriver.ru (Postfix) with ESMTPSA id 26F505AE6 for ; Wed, 9 May 2012 12:15:51 +0400 (MSK) Date: Wed, 9 May 2012 12:15:42 +0400 From: Peter Vereshagin To: freebsd-questions@freebsd.org Message-ID: <20120509081541.GA12699@external.screwed.box> References: <898E0B3D-63DD-470C-8F1D-49F478D05C7E@gmail.com> <4FA92EDA.3090809@infracaninophile.co.uk> <20120508155536.505fd7ed@scorpio> <4FA98765.3020702@infracaninophile.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <4FA98765.3020702@infracaninophile.co.uk> Organization: ' X-Face: 8T>{1owI$Byj]]a; ^G]kRf*dkq>E-3':F>4ODP[#X4s"dr?^b&2G@'3lukno]A1wvJ_L(~u 6>I2ra/<,j1%@C[LN=>p#_}RIV+#:KTszp-X$bQOj,K Subject: Re: securing MySQL: easiest/best ways? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 May 2012 08:15:59 -0000 Hello. 2012/05/08 21:51:49 +0100 Matthew Seaman => To freebsd-questions@freebsd.org : MS> data dir shared between two servers. Keeping the configs with the data MS> does have a few advantages. I know yet another reason to do this. In common case this isn't mysql-specific. There may be a 'chroot' feature built into the daemon like mysqld that means that daemon does chroot(2) first when it is running, and the directory to chroot is the its own data directory, say, /var/db/mysql. This way it should be able to re-read its configuration file on receiving, say HUP or USR1 posix signal to chenge its settings on the fly. This is why in this particular case the configuration file must reside within the databse directory. -- Peter Vereshagin (http://vereshagin.org) pgp: A0E26627