Hello, The bind address is the address on which the MySQL service will reside on and respond from IIRC. That means if you have a public facing server with a MySQL instance you want to share on a private network, you can bind it to the private IP address. Makes it only possible to access from your private network. A practical example of this would be a web server striding your DMZ and private network that you want to have internal access to the database from. You wouldn't want to expose MySQL to the world in this setup.
The second level checks are for restricting users to addresses. That means you could have user accounts that are only accessible from certain machines (e.g. restrict the replication user to certain machines). It's a PITA when you've got a simple, small Rivendell setup but handy when you've got more complicated systems and configurations to support. Regards, Marc. On 6 April 2013 14:34, Fred Gleason <[email protected]> wrote: > On Apr 6, 2013, at 07:35 16, Alan Smith wrote: > > > Why the two separate IP address checks???? > > You would need to ask the MySQL designers. It's been that way for as long > as I can remember. > > Cheers! > > > |-------------------------------------------------------------------------| > | Frederick F. Gleason, Jr. | Chief Developer | > | | Paravel Systems | > |-------------------------------------------------------------------------| > | A room without books is like a body without a soul. | > | -- Cicero | > |-------------------------------------------------------------------------| > > _______________________________________________ > Rivendell-dev mailing list > [email protected] > http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev >
_______________________________________________ Rivendell-dev mailing list [email protected] http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev
