On Mon, August 13, 2007 10:37 am, Paul G. Allen wrote: > On Sun, 2007-08-12 at 08:23 -0700, Lan Barnes wrote: > >> >> As best I can tell, the 192.168.1.0/255.255.255.0 semantics is a mysql >> thing (from the documentation on mysql.org) meaning "requesting IP & >> mask >> == this IP". It is yet another expression of 192.168.100.%. >> >> One of my gripes about mysql so far is that I have seen so many ways of >> expressing this wildcardness, and a lot of them haven't worked. Some >> people report that they have no joy until they enter a rule explicitly >> for >> each remote FE's IP. > > I have never, ever had to do this. I have one rule for my databases that > allows connections from all IPs on the LAN, and one rule that allows > connections from localhost. No problems at all. > > For all IPs, the rule is 'lsuser'@'%' > For localhost is is 'lsuser'@'localhost' > > I have found the best way to set up users and privileges is to use the > MySQL Administrator. When I install a MySQL DB, I also install the GUI > tools. I then connect to the DB engine using the admin tool (as the > MySQL root user) and setup an initial user account that has admin > privileges. At that time, I also change the root password from the > default. I will then create other accounts as needed. > > Using the GUI I am certain that the accounts and privileges are set up > correctly and that I am not making syntax errors or other mistakes that > may cause me grief later. > > PGA >
I will put this in my Tips file. For now, it's working and I am loath to try to improve on that. -- Lan Barnes SCM Analyst Linux Guy Tcl/Tk Enthusiast Biodiesel Brewer -- KPLUG-List@kernel-panic.org http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
