Date: Wed, 9 May 2012 12:15:42 +0400 From: Peter Vereshagin <peter@vereshagin.org> To: freebsd-questions@freebsd.org Subject: Re: securing MySQL: easiest/best ways? Message-ID: <20120509081541.GA12699@external.screwed.box> In-Reply-To: <4FA98765.3020702@infracaninophile.co.uk> References: <898E0B3D-63DD-470C-8F1D-49F478D05C7E@gmail.com> <4FA92EDA.3090809@infracaninophile.co.uk> <20120508155536.505fd7ed@scorpio> <4FA98765.3020702@infracaninophile.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello. 2012/05/08 21:51:49 +0100 Matthew Seaman <m.seaman@infracaninophile.co.uk> => 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 <peter@vereshagin.org> (http://vereshagin.org) pgp: A0E26627
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120509081541.GA12699>