securing MySQL: easiest/best ways?
peter at vereshagin.org
Wed May 9 08:15:59 UTC 2012
2012/05/08 21:51:49 +0100 Matthew Seaman <m.seaman at infracaninophile.co.uk> => To freebsd-questions at 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 at vereshagin.org> (http://vereshagin.org) pgp: A0E26627
More information about the freebsd-questions