<div dir="ltr">Finally got back to this [too busy doing more important things like watching new shows ;-)].<div><br></div><div>I had tried the command as described by Karl (without the FLUSH PRIVILEGES, BTW), but was thrown of by two things. One, the password matched the one for 'mythtv'@'%', and two, the command SQL system response of "Query OK, 0 rows affected (0.00 sec)" made me think that nothing changed.</div>
<div><br></div><div>This time, I made the password something entirely bogus, literally setting it to be mythtv_pwd. I got the same SQL response, but when I queried for the values with the command:</div><div> mysql> SELECT host, user, password FROM user;<br>
</div><div>I got different values reported for @'%' and @'localhost'. When I put the password value I actually wanted in place of mythtv_pwd and checked again, the encrypted password values matched, so, I guess that 1) I got it set and 2) it didn't need setting in the first place.</div>
<div><br></div><div>Don't mind the noob. Time to move along. Sigh...</div><div><br></div><div>Thanks for the help.<br></div><div><div class="gmail_extra"><br>--</div><div class="gmail_extra">Craig.</div></div></div>